eHealth Infrastructure
3.0.0 - release

eHealth Infrastructure - Local Development build (v3.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: ehealth-composition

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-composition Version: 3.0.0
Active as of 2024-05-16 Computable Name: ehealth-composition

Introduction

A set of healthcare-related information that is assembled together into a single logical document that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained.

Scope and Usage

In scope of the eHealth infrastructure, the Composition is used primarily for internal use when assembling resources into documents during publication to national document sharing.

When retrieving documents from national document sharing, these are represented as Clinical Document Architecture (CDA) XML documents. When choosing to transform the content to FHIR resources, the resulting Composition is the FHIR resource tying the other, resulting resources together as a document.

Usage:

Formal Views of Profile Content

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

This structure is derived from Composition

NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition 0..*CompositionA set of resources composed into a single coherent clinical statement with clinical attestation
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... authorOrganization 0..*Reference(ehealth-organization) {b, c}Organization that authored the Composition
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-composition-authorOrganization
... type 1..1CodeableConceptKind of composition (LOINC if possible)
Binding: Document Type (required)
... subject 1..1Reference(Resource)Who and/or what the composition is about
... encounter 0..1Reference(Encounter) {b, c}Context of the Composition
... author 1..*Reference(ehealth-practitioner | ehealth-device | ehealth-patient | ehealth-relatedperson)Who and/or what authored the composition
... attester
.... party 0..1Reference(ehealth-patient | ehealth-practitioner | ehealth-organization)Who attested the composition
... custodian 0..1Reference(ehealth-organization) {b, c}Organization which maintains the composition
... relatesTo
.... Slices for target[x] 1..1Identifier, Reference(Composition)Target of the relationship
Slice: Unordered, Open by type:$this
..... target[x]:targetIdentifier 0..1IdentifierTarget of the relationship
..... target[x]:targetReference 0..1Reference(ehealth-composition)Target of the relationship
... event
.... code 0..*CodeableConceptCode(s) that apply to the event being documented
Binding: Event Type Codes (required)

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Composition.typerequiredDocumentType
http://ehealth.sundhed.dk/vs/document-type
from this IG
Composition.categoryrequiredDocumentClass
http://ehealth.sundhed.dk/vs/document-class
from this IG
Composition.event.coderequiredEventTypeCodes
http://ehealth.sundhed.dk/vs/event-type-codes
from this IG

 

Other representations of profile: CSV, Excel, Schematron