Basisprofil for Norwegian Endpoint information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. The profile adds Norwegian specific identification of Endpoing. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

Resource profile for definition of electronic endpoints used by healthcare organizations to communicate using different protocols. The norwegian profile use-case is to represent endpoints for electronic communication. Fallback solutions using mail or fax has to be indexed in the norwegian master index for healthcare organizations and are not described using this profile.

Basisprofil for Norwegian Location information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. Should be used as a basis for further profiling in use-cases where specific location information is needed. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

Basisprofil for Norwegian Organization information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. The basis profile describes information structures typically used for identifying norwegian organizations. Should be used as a basis for further profiling in use-cases where other specific identity information is needed. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

Basisprofil for Norwegian Patient information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. Should be used as a basis for further profiling in use-cases where specific identity information is needed. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

Basisprofil for Norwegian Practitioner information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. Should be used as a basis for further profiling in use-cases where specific identity information is needed. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

2019-03 - The no-basis-Practitioner resource main use-case is to represent the actual Practitioner, e.g. a person. The resource can include information about how to identify the practitioner in addition to the practitioner’s education, qualifications and speciality. The resource can also include approvals and other centrally registered capabilities recorded for the practitioner.

Basisprofil for Norwegian Address information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. The profile adds Norwegian specific property information, official use of address and further explanation of the use for the data-elements in a Norwegian address. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

Basisprofil for Norwegian HumanName. Defined by The Norwegian Directorate of eHealth and HL7 Norway. The profile adds the concept of middlename and further explains of the use for the data-elements in a Norwegian context. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

Defines the concept of an officialy registered address in Norway. Usually this will be the adress registered in “Folkeregisteret” for persons or “Enhetsregisteret” for organizations.

The basis extension defines the Norwegian middlename wich is called “mellomnavn” and defined by Norwegian legislation (Lov om personnavn).

Coded value for municipality/county Norwegian kommune

This basis extension describes information identifying norwegian real property.

Simple extension containing information about what part of a norwegian city the patient is a resident. Administrative purpose.

ValueSet for connection types used in Endpoint definition. Includes all Norwegian specific types (no-basis-connection-type) and the extensible HL7 CodeSystem for connection-type

ValueSet for location types used in Location definition. Includes all Norwegian specific types (no-basis-location-type.codesystem) and all codes from v3.ServiceDeliveryLocationRoleType defined by HL7

Codes to describe Norwegian message based communication protocols.

Additional codes for location.type used by no-basis-Location

Observation example based on room sensor Device 001

Observation example based on room sensor Device 002

Patient Jannice Soreng taken from no-basis FSH instances

Bundle collection for BVC and MADRS observations made by practitioner with reference to room but not patient

Condition used to describe patient Jannice Soreng’s diagnosis

Condition used to describe patient Jannice Soreng’s diagnosis

Condition used to describe patient Jannice Soreng’s diagnosis

Device 001 sending the alert from main room

Device 002 sending the alert from bathroom

CarePlan used to connect patient Jannice Soreng to Post D Room 34

Episode of Care used to define period of care for Jannice Soreng and link to her care manager Kumar Magnar

Location for a room collection for manually registered observation

Location for a room part for device registered observation

Location for a hospital ward based on RESH id

Organization location for the clinic based on its Her-ID

Example of a practitioner Kumar Magnar with both HPR and FNR ids