Interacting with Services in the Administrative Domain

These pages describe interactions with services in the eHealth Infrastructure’s Administrative Domain. Common to these services and their FHIR resources is that they are generic in the sense non patient specific. Also common is that these resources are used when creating patient specific resources in the Clinical Domain.

The following Administrative Domain FHIR resources constitute reference data:

FHIR Resource

eHealth Profile

Managing It

Using It

FHIR Resource

eHealth Profile

Managing It

Using It

FHIR Organization

ehealth-organization - https://ehealth.sundhed.dk/fhir/StructureDefinition-ehealth-organization.html

Managing an Organization

Most Organization resources are managed automatically as imported as described in Importing and updating Organization information from SOR and FK-Organisation into eHealth Infrastructure

Using Organization, CareTeam and Practitioner

FHIR Practitioner

ehealth-practitioner - https://ehealth.sundhed.dk/fhir/StructureDefinition-ehealth-practitioner.html

Created as described in Behind the Scenes | Handling at Login

Using Organization, CareTeam and Practitioner

FHIR CareTeam

ehealth-careteam - https://ehealth.sundhed.dk/fhir/StructureDefinition-ehealth-careteam.html

Managing a CareTeam

Using Organization, CareTeam and Practitioner

FHIR PractitionerRole

ehealth-practitionerrole - https://ehealth.sundhed.dk/fhir/StructureDefinition-ehealth-practitionerrole.html

Created as described in Behind the Scenes | Handling at Login

 

Telemedicine plan templates and rules are captured in:

FHIR Resource

eHealth Profile

Managing It

Using It

In addition, the Administrative Domain contains the following terminology FHIR resources that are not profiled:

The use of terminology resources are described in

https://www.hl7.org/fhir/terminology-module.html

and there is further explanation (in Danish) at https://docs.ehealth.sundhed.dk/latest-released/trifolia/governance/index.html#_brug_af_terminologi_i_ehealth_infrastrukturen .

There exists a secondary Terminology service (Questionnaire Terminology Service), which includes the same FHIR resource types, but contains CodeSystems and NamingSystems for the specific purpose of supporting document sharing.

Please consult the Terminology service CapabilityStatement for a list of operations supported by it, as not all listed in Terminology Module are supported.