hl7dk · j3h4 · Jun 16, 2025 · Feb 13, 2025 · May 1, 2025 · May 1, 2025
diff --git a/input/fsh/DkCoreEncounter.fsh b/input/fsh/DkCoreEncounter.fsh
@@ -0,0 +1,22 @@
+Profile: DkCoreEncounter
+Parent: Encounter
+Id: dk-core-encounter
+Title: "Danish Core Encounter Profile"
+Description: "HL7 Denmark core profile for an encounter"
+* extension contains
+    PlannedStartDate named plannedStartDate 0..1 and
+    PlannedEndDate named plannedEndDate 0..1 and
+    CareProvider named careProvider 0..1
+* extension[plannedStartDate] ^short = "The planned start date/time (or admission date) of the encounter"
+* extension[plannedEndDate] ^short = "The planned end date/time (or discharge date) of the encounter"
+* extension[careProvider] ^short = "The organization (facility) responsible for the care of the patient during this encounter"
+* priority from DkCoreEncounterPriority (extensible)
+* subject only Reference(DkCorePatient)
+* diagnosis ^slicing.discriminator.type = #type
+* diagnosis ^slicing.discriminator.path = condition
+* diagnosis ^slicing.rules = #open
+* diagnosis ^slicing.description = "Slicing based on condition type"
+* diagnosis contains dk-core-conditions 0..*
+* diagnosis[dk-core-conditions].condition only Reference(DkCoreCondition)
+* diagnosis[dk-core-conditions].rank 1..1
+* serviceProvider only Reference(DkCoreOrganization)
diff --git a/input/fsh/aliases.fsh b/input/fsh/aliases.fsh
@@ -27,5 +27,4 @@ Alias: $observation-bp = http://hl7.org/fhir/StructureDefinition/bp
 Alias: $LOINC-vitalsigns = http://hl7.org/fhir/ValueSet/observation-vitalsignresult
 Alias: $v3-Confidentiality = http://terminology.hl7.org/CodeSystem/v3-Confidentiality
 Alias: $v3-RoleCode = http://terminology.hl7.org/CodeSystem/v3-RoleCode
-
-
+Alias: $v3-ActPriority = http://terminology.hl7.org/CodeSystem/v3-ActPriority
diff --git a/input/fsh/codeSystems.fsh b/input/fsh/codeSystems.fsh
@@ -1304,4 +1304,4 @@ Description: "DK NPU Subsetted code system used in DK Core. The full version of
   * ^property[+].code = #status
   * ^property[=].valueCode = #active
   * ^property[+].code = #comment
-  * ^property[=].valueString = "Unit defined"
+  * ^property[=].valueString = "Unit defined"
diff --git a/input/fsh/extensions.fsh b/input/fsh/extensions.fsh
@@ -42,4 +42,31 @@ Description: "Identifier holding the official identifier for a danish municipali
 * . ^short = "Danish Core Municipality codes"
   * ^definition = "Identifier holding the official identifier for a danish municipality"
 * value[x] only CodeableConcept
-  * coding from MunicipalityCodes (required)
+  * coding from MunicipalityCodes (required)
+
+Extension: PlannedStartDate
+Id: dk-core-planned-start-date
+Title: "PlannedStartDate"
+* . ^short = "PlannedStartDate"
+  * ^definition = "The planned start date/time (or admission date) of the encounter"
+* value[x] only dateTime
+* ^context.type = http://hl7.org/fhir/extension-context-type#element
+* ^context.expression = "Encounter"
+
+Extension: PlannedEndDate
+Id: dk-core-planned-end-date
+Title: "PlannedEndDate"
+* . ^short = "PlannedEndDate"
+  * ^definition = "The planned end date/time (or discharge date) of the encounter"
+* value[x] only dateTime
+* ^context.type = http://hl7.org/fhir/extension-context-type#element
+* ^context.expression = "Encounter"
+
+Extension: CareProvider
+Id: dk-core-care-provider
+Title: "CareProvider"
+* . ^short = "CareProvider"
+  * ^definition = "The organization (facility) reponsible for the care of the patient during this encounter"
+* value[x] only Reference(DkCoreOrganization)
+* ^context.type = http://hl7.org/fhir/extension-context-type#element
+* ^context.expression = "Encounter"
diff --git a/input/fsh/valueSets.fsh b/input/fsh/valueSets.fsh
@@ -841,6 +841,14 @@ Description: "Value set used for indicating the organization type for organizati
 *  $sct#255203001
 *  $sct#264372000
 
+ValueSet: DkCoreEncounterPriority
+Id: dk-core-encounter-priority
+Title: "DK priority codes for encounters"
+Description: "Value set used for indicating priority of an encounter"
+* ^experimental = false
+* ^status = #active
+*  $v3-ActPriority#A
+*  $v3-ActPriority#EL
 
 ValueSet: SorPracticeSettingCode
 Id: dk-core-practice-setting-code

diff --git a/input/pagecontent/StructureDefinition-dk-core-encounter-intro.md b/input/pagecontent/StructureDefinition-dk-core-encounter-intro.md
@@ -0,0 +1,41 @@
+### Scope and usage
+This profile is intended to encapsulate information about encounters in the Danish health sectors.
+
+### Responsibilities for treatment and care
+In Denmark there is a distinguishment between which organization has the reponsibility for providing treatment to the patient, and which organization
+has the responsibility for providing care to the patient.
+
+* Treatment responsibility ([DA] behandlingsansvarlig): this lies with the service provider organization
+* Care responsibility ([DA] plejeansvarlig): this lies with the organization where the patient has a stay (is hospitalized)
+
+The treatment responsibility is represented by Encounter.serviceProvider and the current care responsibility is represented by the
+extension [CareProvider](./StructureDefinition-dk-core-care-provider.html).
+
+## Specifying primary and secondary diagnosis
+Hospital encounters in Denmark have diagnosis associated that specifies the primary diagnosis beeing treated ([DA] aktionsdiagnose) and secondary diagnosis ([DA] bidiagnose) that might be relevant to the treatment of the primary diagnosis. These can be given in the diagnosis element and it is recommended to use the rank element to distinguish between primary and secondary diagnoses, the primary being given rank 1 and the secondary a rank > 1.
+
+### Handling future versions
+In FHIR R5 and newer, there have been made significant changes to Encounter profile.
+
+In order to be compatible with the changes to the value set bound to Encounter.class in FHIR R5 and newer, we recommend to restrict to using only
+the values from the FHIR R5 value set [Encounter class](https://terminology.hl7.org/5.2.0/ValueSet-encounter-class.html), which is a subset of the
+FHIR R4 value set [ActEncounterCode](https://hl7.org/fhir/R4/v3/ActEncounterCode/vs.html):
+
+{:class="grid"}
+| Code | Display | Typical use in Denmark |
+| ---- | ------- | -------------- |
+| IMP | inpatient encounter | Encounters where patients are admitted typically for more than 12 hours. |
+| AMB | ambulatory | Encounters where patients are not admitted. |
+| OBSENC | observation encounter | Not used. |
+| EMER | emergency | Encounters where patients are admitted to an emergency ward typically for up to 72 hours. |
+| VR | virtual | Virtual encounters with patients typically using televideo, telephone, or other means of telepresence. |
+| HH | home health | Encounters with patients in their own home. |
+
+Note that Encounter.class has an extensible binding, so if a class coding not part of the bound value set is needed, it is allowed to use an
+alternate coding.
+
+In order to support the addition of Encounter.plannedStartDate and Encounter.plannedEndDate in FHIR R5, the extensions
+[PlannedStartDate](./StructureDefinition-dk-core-planned-start-date.html) and [PlannedEndDate](./StructureDefinition-dk-core-planned-end-date.html)
+have been added to DkCore. However, note that in the R4 documentation it is stated that a planned start date could be given by placing
+period.start in the future, and setting the status to ‘planned’. As a consequence, this practice is also acceptable in the dk-core R4 version, 
+but the use of plannedStart and plannedEnd extensions are encouraged to make transition to future FHIR versions easier.
diff --git a/input/pagecontent/index.md b/input/pagecontent/index.md
@@ -42,7 +42,7 @@ Issues opened in that GitHub repo are very welcome. They help the affiliate pick
 Pull requests are even better. If you are in a position to suggest how exactly your proposal should be implemented in the specification, do it! It helps the team maintaining the implementation guide a great deal.
 
 ### Language
-The main language of this implementation guide, and the profiles in it, is English. Content that does not have an official English term uses a Danish term instead. Sometimes terms are explained using both Danish and English. Danish terms and explanations are prefixed with 'Da'
+The main language of this implementation guide, and the profiles in it, is English. Content that does not have an official English term uses a Danish term instead. Sometimes terms are explained using both Danish and English. Danish terms and explanations are prefixed with [DA]
 
 ### Connection between dk-core and common Danish architectures and standards
 HL7 Denmark includes common Danish architectures and standards if relevant, when content is added to dk-core. This section provides information about principle decisions as well as more specific ones that require explanations.

diff --git a/sushi-config.yaml b/sushi-config.yaml
@@ -53,6 +53,7 @@ version: 3.5.0
 #Flip status to 'active' for publication. Flip to 'draft' for CI
 status: draft
 #status: active
+
 #Flip releaseLabel to 'release' for publication. Flip to 'ci-build' for CI
 releaseLabel: ci-build
-#releaseLabel: release
+#releaseLabel: release