Entities

HL7 Norway proposed basis profiles for Entity resources in HL7 FHIR.

Only attributes with actual profiling is included in the information model diagram.

no-basis-Endpoint

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

Endpoint for both for tjenestebasert adressering and other use-cases. Link to the full documentation of the profile no-basis-Endpoint

Resource content

identifier
connectionTypeBinding
managingOrganizationReference(Organization | no-basis-Organization)
meldingensFunksjonBinding
formatCodeBinding
payloadMimeTypeBinding
address

no-basis-HealthCareService

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

Link to the full documentation of the profile no-basis-HealthcareService

Resource content

identifier
systemI
category
type
system1..Fixed Value
code1..
system1..Fixed Value
code1..
system1..Fixed Value
code1..
system1..Fixed Value
code1..
locationReference(Location | no-basis-Location)
endpointReference(Endpoint | no-basis-Endpoint)

no-basis-Organization

Basisprofil for Norwegian Organization 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 restrict further the information elements according to specification relevant to the use-case.

The full documentation of the profile no-basis-Organization

Resource content

system1..Fixed Value
value1..
system1..Fixed Value
value1..
system1..Fixed Value
code1..
system1..Fixed Value
code1..
addressno-basis-Address
partOfReference(Organization | no-basis-Organization)
addressno-basis-Address
endpoint

Example

Example organization resource conformant to no-basis-Organization profile: Direktoratet for e-Helse

The HER-id and Organization

The HERid SHALL not be assigned on the Organizational level. The Organizations registered in adresseregisteret uses the HERid for message based addressing.

no-basis-Location

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.

The full documentation of the profile no-basis-Location

Resource content

addressno-basis-Address
managingOrganizationReference(Organization | no-basis-Organization)
endpointReference(Endpoint | no-basis-Endpoint)

no-basis-DocumentReference

Basisprofil for Norwegian DocumentReference information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. This profile identifies a set of minimum expectations for a DocumentReference resource when creating, searching and retrieving documents by defining which coding system(s) must be present when using this profile.

The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

Link to the full documentation of the profile no-basis-DocumentReference

Resource content

typeBinding

no-basis-Composition

Basisprofil for Norwegian Composition information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. This profile identifies a set of minimum expectations for a Composition resource when creating, searching and retrieving compositions by defining which coding system(s) must be present when using this profile.

The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

Link to the full documentation of the profile no-basis-Composition

Resource content

typeBinding