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

StructureDefinition: ehealth-patient

Formal Views of Profile Content

The official URL for this profile is:

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

This profile holds the patient information needed in the danish eHealth context. Patients models the concept of a person in a careplan process. All patients must be linked to an actual person resource instance, where the person acts a template for a patient. A newly created patient is always based from a person which also means that a person links to all its patients.

Creating patients

Patients can only be created using the operations defined for the Patient resource. The operations ensure that patients are created with the proper demographics data, the proper managing organization and under the proper legislation and having a proper link between person and patient.

This profile builds on Patient.

This profile was published on Thu May 16 12:32:10 UTC 2019 as a draft by ehealth.sundhed.dk.

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

 

Terminology Bindings

Path	Name	Conformance	ValueSet
Patient.language	Common Languages	extensible	Common Languages
Patient.telecom.system	ContactPointSystem	required	ContactPointSystem
Patient.telecom.system	ContactPointSystem	required	ContactPointSystem
Patient.gender	AdministrativeGender	required	AdministrativeGender
Patient.address.use	AddressUse	required	AddressUse
Patient.address.type	AddressType	required	AddressType
Patient.address.use	AddressUse	required	AddressUse
Patient.address.type	AddressType	required	AddressType
Patient.maritalStatus	Marital Status Codes	extensible	Marital Status Codes
Patient.contact.relationship	v2 Contact Role	extensible	v2 Contact Role
Patient.contact.gender	AdministrativeGender	required	AdministrativeGender
Patient.animal.species	AnimalSpecies	example	AnimalSpecies
Patient.animal.breed	AnimalBreeds	example	AnimalBreeds
Patient.animal.genderStatus	GenderStatus	example	GenderStatus
Patient.communication.language	Common Languages	extensible	Common Languages
Patient.link.type	LinkType	required	LinkType

Constraints

Id	Path	Details	Requirements
dom-2	Patient	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-1	Patient	If the resource is contained in another resource, it SHALL NOT contain any narrative : contained.text.empty()
dom-4	Patient	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	Patient	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()
ele-1	Patient.contact	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
pat-1	Patient.contact	SHALL at least contain a contact's details or a reference to an organization : name.exists() or telecom.exists() or address.exists() or organization.exists()
ele-1	Patient.communication	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ele-1	Patient.link	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())

.