HL7 FHIR Implementation Guide: DK Core
1.1.0 - release

This page is part of the HL7 FHIR Implementation Guide: DK Core (v1.1.0: Release) based on FHIR R4. The current version which supercedes this version is 2.0.0. For a full list of available versions, see the Directory of published versions

Resource Profile: Danish Core Patient Profile

Defining URL:http://hl7.dk/fhir/core/StructureDefinition/dk-core-patient
Version:1.1.0
Name:DkCorePatient
Title:Danish Core Patient Profile
Status:Active as of 2/4/20
Definition:

HL7 Denmark core profile for a patient

Publisher:HL7 Denmark
Copyright:

CC-BY-SA-4.0

Source Resource:XML / JSON / Turtle

The official URL for this profile is: 

http://hl7.dk/fhir/core/StructureDefinition/dk-core-patient

Introduction

The Danish Core Patient profile is intended to encapsulate the most common and basic data model of patients in danish healthcare systems covering both primary sector (GP’s), secondary sector (specialty doctors and hospitals) and municipality cases. As such the profile should be usable in most danish contexts.

Use of patient identifiers

This patient profile currently only reflects the use of the established national danish patient identifiers called CPR. More official identifiers are expected to be used and profiled in the future, eg:

Use of security label on patients

Danish citizens that have requested name and address protection (Navne- og adressebeskyttelse) should be labeled with the security label as follows:

 <Patient xmlns="http://hl7.org/fhir">
  <meta>
    <security>
      <system value="http://terminology.hl7.org/CodeSystem/v3-Confidentiality"/>
      <code value="R"/>
      <display value="Restricted"/>
    </security>
  </meta>
...  [snip] ...
</Patient>

Use of this label should be interpreted according to the law, rouhgly meaning that only personnel using systems in public/official affairs are allowed to see name and address for the patient/citizen.

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Patient

Summary

Mandatory: 1 element (2 nested mandatory elements)
Must-Support: 2 elements
Fixed Value: 1 element

Structures

This structure refers to these other structures:

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element Patient.identifier is sliced based on the value of value:system
  • The element Patient.name is sliced based on the value of value:use
  • The element Patient.generalPractitioner is sliced based on the value of value:identifier.system

 

Other representations of profile: CSV, Excel, Schematron

Terminology Bindings

PathConformanceValueSet / Code
Patient.languagepreferredCommonLanguages
Max Binding: AllLanguages
Patient.name:official.userequiredFixed Value: official
Patient.genderrequiredAdministrativeGender
Patient.address.userequiredAddressUse
Patient.address.typerequiredAddressType
Patient.maritalStatusextensibleDK Marital Status Codes
Patient.contact.relationshipextensiblePatientContactRelationship
Patient.contact.genderrequiredAdministrativeGender
Patient.communication.languagepreferredCommonLanguages
Max Binding: AllLanguages
Patient.generalPractitioner:referencedSORUnit.typeextensibleResourceType
Patient.link.typerequiredLinkType

Constraints

IdGradePathDetailsRequirements
pat-1errorPatient.contactSHALL at least contain a contact's details or a reference to an organization
: name.exists() or telecom.exists() or address.exists() or organization.exists()

Notes:

Note: feedback is most welcome and should be directed to the danish affiliate’s github repository (https://github.com/hl7dk/dk-core/).