• Content
• Detailed Descriptions
• Examples
• Example operations
• XML
• JSON

StructureDefinition: ehealth-correspondance

Formal Views of Profile Content

The official URL for this profile is:

http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-correspondance

This is the profile for correspondance messages, which are also known as "XDIS91" in existing terminology. It covers messages between health professionals concerning a specific patient/subject, eg. a descriptions of a specific treatment going from hospital to doctor. . The correspondance message may contain different types of attachments. These are reflected in the provided example "correspondance-all-types", which contains all four types. The type of the individual attachments are specified using the referencetype extension. The types are:

• clinicalinformation: For the most usual case: clinical information about the subject (base64-encoded in the data section)
• url: For references to external URLs
• sup: To specify if additional data exists in the SUP database
• attachment: For binary attachments, eg. images, PDF documents etc. These are included base64-encoded in the data section)

For remaining document data, see the corresponding value sets.

This profile builds on Communication.

This profile was published on Tue Mar 31 08:26:16 UTC 2020 as a draft by ehealth.sundhed.dk.

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

 

Terminology Bindings

Path	Conformance	ValueSet
Communication.language	extensible	Common Languages Max Binding: All Languages
Communication.identifier:envelopeIdentifier.use	required	IdentifierUse
Communication.identifier:envelopeIdentifier.type	extensible	Identifier Type Codes
Communication.identifier:letterIdentifier.use	required	IdentifierUse
Communication.identifier:letterIdentifier.type	extensible	Identifier Type Codes
Communication.status	required	EventStatus
Communication.notDoneReason	example	CommunicationNotDoneReason
Communication.category	example	CommunicationCategory
Communication.category:acknowledgementCode	example	CommunicationCategory
Communication.category:versionCode	example	CommunicationCategory
Communication.category:typeCode	example	CommunicationCategory
Communication.category:statusCode	example	CommunicationCategory
Communication.medium	example	v3 Code System ParticipationMode
Communication.subject.identifier.use	required	IdentifierUse
Communication.subject.identifier.type	extensible	Identifier Type Codes
Communication.reasonCode	example	SNOMED CT Clinical Findings
Communication.payload.content[x]:contentAttachment.contentType	required	http://hl7.org/fhir/ValueSet/mimetypes
Communication.payload.content[x]:contentAttachment.language	extensible	Common Languages Max Binding: All Languages

Constraints

Id	Path	Details	Requirements
dom-2	Communication	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-1	Communication	If the resource is contained in another resource, it SHALL NOT contain any narrative : contained.text.empty()
dom-4	Communication	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3	Communication	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource : contained.where(('#'+id in %resource.descendants().reference).not()).empty()
com-1	Communication	Not Done Reason can only be specified if NotDone is "true" : notDone or notDoneReason.exists().not()
ele-1	Communication.extension:authorizationTime	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ext-1	Communication.extension:authorizationTime	Must have either extensions or value[x], not both : extension.exists() != value.exists()
ele-1	Communication.payload	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())

.