3. Artifact index
3.1. FHIR profiles
3.1.1. DocumentReference
In the current version of this IG, the IHE.MHD.Comprehensive.DocumentReference profile is used as a base profile for the ITI-67 and ITI-68 based transactions. The bbs-DocumentReference profile is derived from the former profile, and contains mappings to the Nictiz BBS dataset (1.0.0-alpha.2), as well as the National IHE MetaData Set (2024), which were provided in section 5.3 of the BBS FHIR IG. Moreover, mappings to the MedMij dataset have been added for concepts that have been introduced in the MedMij use case.
BbsDocumentReference (DocumentReference) | C | ComprehensiveDocumentReference | Element idDocumentReferenceShort description ImagingResearch Alternate namesOnderzoek DefinitionImaging research including images and reports. Usually, this is used for documents other than those defined by FHIR. ComprehensiveDocumentReference Constraints
| |||
id | Σ | 0..1 | id | There are no (further) constraints on this element Element idDocumentReference.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDocumentReference.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.meta.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.meta.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
versionId | Σ | 0..1 | id | There are no (further) constraints on this element Element idDocumentReference.meta.versionIdShort description Version specific identifier DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
| ||
lastUpdated | Σ | 0..1 | instant | There are no (further) constraints on this element Element idDocumentReference.meta.lastUpdatedShort description When the resource version last changed DefinitionWhen the resource last changed - e.g. when the version changed. This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
| ||
source | Σ | 0..1 | uri | There are no (further) constraints on this element Element idDocumentReference.meta.sourceShort description Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
| ||
profile | Σ | 0..* | canonical(StructureDefinition) | There are no (further) constraints on this element Element idDocumentReference.meta.profileShort description Profiles this resource claims to conform to DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) Constraints
| ||
security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idDocumentReference.meta.securityShort description Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible) Constraints
| ||
tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDocumentReference.meta.tagShort description Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
| ||
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDocumentReference.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
| ||
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDocumentReference.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |||
text | 0..1 | Narrative | There are no (further) constraints on this element Element idDocumentReference.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |||
contained | 0..* | Resource | There are no (further) constraints on this element Element idDocumentReference.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
| ||
modifierExtension | ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idDocumentReference.modifierExtensionShort description Extension DefinitionAn Extension
| ||
masterIdentifier | 1..1 | UniqueIdIdentifier | Element idDocumentReference.masterIdentifierShort description ReportInformationIdentificationNumber / ImageInformationIdentificationNumber / UniqueID Alternate namesVerslaginformatieIdentificatienummer, BeeldinformatieIdentificatienummer Definition
The structure and format of this Id shall be consistent with the specification corresponding to the formatCode attribute. (e.g. for a DICOM standard document a 64-character numeric UID, for an HL7 CDA format a serialization of the CDA Document Id extension and root in the form "oid^extension", where OID is a 64 digits max, and the Id is a 16 UTF-8 char max. If the OID is coded without the extension then the '^' character shall not be included.). CDA Document Id extension and root. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
identifier | S Σ | 0..* | Identifier | There are no (further) constraints on this element Element idDocumentReference.identifierShort description Other identifiers for the document DefinitionOther identifiers associated with the document, including version independent identifiers. Unordered, Open, by use(Value) Constraints
| ||
entryUUID | 0..* | EntryUUIDIdentifier | There are no (further) constraints on this element Element idDocumentReference.identifier:entryUUIDShort description An identifier intended for computation DefinitionAn identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
status | Σ ?! | 1..1 | codeBindingPattern | Element idDocumentReference.statusShort description AvailabilityStatus DefinitionThe lifecycle status of the document. This is the status of the DocumentReference object, which might be independent from the docStatus element. This element is labeled as a modifier because the status contains the codes that mark the document or reference as not currently valid. DocumentReferenceStats (required) Constraints
currentMappings
| ||
docStatus | Σ | 0..0 | codeBinding | There are no (further) constraints on this element Element idDocumentReference.docStatusShort description preliminary | final | amended | entered-in-error DefinitionThe status of the underlying document. The document that is pointed to might be in various lifecycle states. Status of the underlying document.
| ||
type | S Σ | 1..1 | CodeableConceptBinding | Element idDocumentReference.typeShort description ProcedureType / TypeCode Alternate namesVerrichtingType Definition
Key metadata element describing the document that describes he exact type of document. Helps humans to assess whether the document is of interest when viewing a list of documents. Precise type of clinical document. VerrichtingTypeDHDCodelijstMetNullFlavor (required) Constraints
| ||
category | S Σ | 1..1 | CodeableConcept | Element idDocumentReference.categoryShort description ClassCode Alternate namesclaxs DefinitionThe code specifying the particular kind of document. Key metadata element describing the the category or classification of the document. This is a broader perspective that groups similar documents based on how they would be used. This is a primary key used in searching. High-level kind of a clinical document at a macro level. DocumentClassValueSet (example) Constraints
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.category.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.category.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
coding | Σ | 2..* | Coding | Element idDocumentReference.category.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by $this(Value) Constraints
| ||
radiologyStudies | Σ | 1..1 | CodingPattern | Element idDocumentReference.category.coding:radiologyStudiesShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
{ "system": "http://loinc.org", "code": "18726-0" }Mappings
| ||
images | Σ C | 0..1 | CodingPattern | Element idDocumentReference.category.coding:imagesShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. The cardinality or value of this element may be affected by these constraints: bbs-DocumentReference-1, bbs-DocumentReference-2 Constraints
{ "system": "urn:oid:1.3.6.1.4.1.19376.1.2.6.1", "code": "IMAGES" }Mappings
| ||
reports | Σ C | 0..1 | CodingPattern | Element idDocumentReference.category.coding:reportsShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. The cardinality or value of this element may be affected by these constraints: bbs-DocumentReference-1 Constraints
{ "system": "urn:oid:1.3.6.1.4.1.19376.1.2.6.1", "code": "REPORTS" }Mappings
| ||
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.category.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
subject | S Σ | 1..1 | Reference(Patient | NlcorePatient) | Element idDocumentReference.subjectShort description Patient / PatientId Alternate namesPatient DefinitionWho or what the document is about. The document can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of farm animals, or a set of patients that share a common exposure). Reference(Patient | NlcorePatient) Constraints
| ||
date | S Σ | 1..1 | instant | Element idDocumentReference.dateShort description DateTime Alternate namesindexed, DatumTijd Definition
Referencing/indexing time is used for tracking, organizing versions and searching.
| ||
author | S Σ | 1..* | Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson) | Element idDocumentReference.authorShort description Author DefinitionIdentifies who is responsible for adding the information to the document. Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant). Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson) Allowed aggregation:contained SlicingUnordered, Open, by resolve()(Profile) Constraints
| ||
location | S Σ | 1..1 | Reference(NlcoreHealthcareProviderOrganization) | Element idDocumentReference.author:locationShort description Location Alternate namesLocatie DefinitionThe healthcare center where the procedure was, is or will be carried out. Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant). Reference(NlcoreHealthcareProviderOrganization) Allowed aggregation:contained Constraints
| ||
performer | S Σ | 0..1 | Reference(NlcoreHealthProfessionalPractitionerRole) | Element idDocumentReference.author:performerShort description Performer Alternate namesUitvoerder DefinitionThe health professional who carried out or will carry out the procedure. In most cases, only the medical specialty is entered, and not the name of the health professional. In the context of image exchange, the Performing Physician should be conveyed here, and NOT the laboratory technician who makes the images (i.e. the Operator). Each occurrence of the zib HealthProfessional is normally represented by two FHIR resources: a PractitionerRole resource (instance of nl-core-HealthProfessional-PractitionerRole) and a Practitioner resource (instance of nl-core-HealthProfessional-Practitioner). The Practitioner resource is referenced from the PractitionerRole instance. For this reason, sending systems should fill the reference to the PractitionerRole instance here, and not the Practitioner resource. Receiving systems can then retrieve the reference to the Practitioner resource from that PractitionerRole instance. In rare circumstances, there is only a Practitioner instance, in which case it is that instance which will be referenced here. However, since this should be the exception, the nl-core-HealthProfessional-Practitioner profile is not explicitly mentioned as a target profile. Reference(NlcoreHealthProfessionalPractitionerRole) Allowed aggregation:contained Constraints
| ||
authenticator | 0..1 | Reference(Practitioner | PractitionerRole | Organization | NlcoreHealthProfessionalPractitionerRole | NlcoreHealthcareProviderOrganization) | Element idDocumentReference.authenticatorShort description LegalAuthenticator DefinitionRepresents a participant who has legally authenticated or attested the document within the author institution. Each occurrence of the zib HealthProfessional is normally represented by two FHIR resources: a PractitionerRole resource (instance of nl-core-HealthProfessional-PractitionerRole) and a Practitioner resource (instance of nl-core-HealthProfessional-Practitioner). The Practitioner resource is referenced from the PractitionerRole instance. For this reason, sending systems should fill the reference to the PractitionerRole instance here, and not the Practitioner resource. Receiving systems can then retrieve the reference to the Practitioner resource from that PractitionerRole instance. In rare circumstances, there is only a Practitioner instance, in which case it is that instance which will be referenced here. However, since this should be the exception, the nl-core-HealthProfessional-Practitioner profile is not explicitly mentioned as a target profile. Reference(Practitioner | PractitionerRole | Organization | NlcoreHealthProfessionalPractitionerRole | NlcoreHealthcareProviderOrganization) Allowed aggregation:contained Constraints
| |||
custodian | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDocumentReference.custodianShort description Organization which maintains the document DefinitionIdentifies the organization or group who is responsible for ongoing maintenance of and access to the document. Identifies the logical organization (software system, vendor, or department) to go to find the current version, where to report issues, etc. This is different from the physical location (URL, disk drive, or server) of the document, which is the technical location of the document, which host may be delegated to the management of some other organization.
| |||
relatesTo | S Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idDocumentReference.relatesToShort description Relationships to other documents DefinitionRelationships that this document has with other document references that already exist. This element is labeled as a modifier because documents that append to other documents are incomplete on their own.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.relatesTo.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.relatesTo.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.relatesTo.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
| ||
code | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idDocumentReference.relatesTo.codeShort description replaces | transforms | signs | appends DefinitionThe type of relationship that this document has with anther document. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document. The type of relationship between documents. DocumentRelationshipType (required) Constraints
| ||
target | Σ | 1..1 | Reference(DocumentReference) | There are no (further) constraints on this element Element idDocumentReference.relatesTo.targetShort description Target of the relationship DefinitionThe target document of this relationship.
| ||
description | Σ | 0..1 | string | Element idDocumentReference.descriptionShort description Comments DefinitionComments associated with the document. Helps humans to assess whether the document is of interest. What the document is about, a terse summary of the document.
| ||
securityLabel | S Σ | 1..* | CodeableConceptBinding | Element idDocumentReference.securityLabelShort description ConfidentialityCode DefinitionThe code specifying the level of confidentiality of the document. Use of the Health Care Privacy/Security Classification (HCS) system of security-tag use is recommended. The confidentiality codes can carry multiple vocabulary items. HL7 has developed an understanding of security and privacy tags that might be desirable in a Document Sharing environment, called HL7 Healthcare Privacy and Security Classification System (HCS). The following specification is recommended but not mandated, as the vocabulary bindings are an administrative domain responsibility. The use of this method is up to the policy domain such as the XDS Affinity Domain or other Trust Domain where all parties including sender and recipients are trusted to appropriately tag and enforce. In the HL7 Healthcare Privacy and Security Classification (HCS) there are code systems specific to Confidentiality, Sensitivity, Integrity, and Handling Caveats. Some values would come from a local vocabulary as they are related to workflow roles and special projects. Security Labels from the Healthcare Privacy and Security Classification System. ConfidentialityCodes (extensible) Constraints
| ||
content | Σ | 1..1 | BackboneElement | There are no (further) constraints on this element Element idDocumentReference.contentShort description Document referenced DefinitionThe document and format referenced.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.content.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.content.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.content.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
| ||
attachment | Σ | 1..1 | Attachment | There are no (further) constraints on this element Element idDocumentReference.content.attachmentShort description Where to access the document DefinitionThe document or URL of the document along with critical metadata to prove content has integrity.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.content.attachment.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.content.attachment.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
contentType | Σ | 1..1 | codeBinding | Element idDocumentReference.content.attachment.contentTypeShort description MimeType DefinitionMIME type of the document. Processors of the data need to be able to know how to interpret the data. The mime type of an attachment. Any valid mime type is allowed.
General text/plain; charset=UTF-8, image/pngMappings
| ||
language | S Σ | 1..1 | codeBinding | Element idDocumentReference.content.attachment.languageShort description LanguageCode DefinitionSpecifies the human language of character data in the document. Using codes from IETF RFC 3066. Users need to be able to choose between the languages in a set of attachments. A human language.
General en-AUMappings
| ||
data | 0..0 | base64Binary | There are no (further) constraints on this element Element idDocumentReference.content.attachment.dataShort description Data inline, base64ed DefinitionThe actual data of the attachment - a sequence of bytes, base64 encoded. The data needs to able to be transmitted inline. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.
| |||
url | Σ | 1..1 | url | Element idDocumentReference.content.attachment.urlShort description URI DefinitionThe URI for the document. The data needs to be transmitted by reference. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.
General http://www.acme.com/logo-small.pngMappings
| ||
size | Σ | 0..1 | unsignedInt | Element idDocumentReference.content.attachment.sizeShort description Size DefinitionSize in bytes of the document. Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.
| ||
hash | Σ | 0..1 | base64Binary | Element idDocumentReference.content.attachment.hashShort description Hash DefinitionHash of the document itself. Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version). The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature.
| ||
title | Σ | 1..1 | string | Element idDocumentReference.content.attachment.titleShort description ReportTitle / ImageTitle / Title Alternate namesVerslagTitel, BeeldTitel Definition
Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer.
General Official Corporate LogoMappings
| ||
creation | S Σ | 1..1 | dateTime | Element idDocumentReference.content.attachment.creationShort description DateTime / CreationTime Alternate namesDatumTijd Definition
This is often tracked as an integrity issue for use of the attachment.
| ||
format | S Σ | 1..1 | CodingBinding | Element idDocumentReference.content.formatShort description FormatCode DefinitionCode globally uniquely specifying the format of the document. Note that while IHE mostly issues URNs for format types, not all documents can be identified by a URI.
| ||
context | Σ | 1..1 | BackboneElement | There are no (further) constraints on this element Element idDocumentReference.contextShort description Clinical context of document DefinitionThe clinical context in which the document was prepared. These values are primarily added to help with searching for interesting/relevant documents.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.context.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
| ||
modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.context.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
| ||
encounter | 0..* | Reference(Encounter | EpisodeOfCare | NlcoreEncounter) | Element idDocumentReference.context.encounterShort description ReferenceIdList DefinitionA list of identifiers that apply to the document. Identifiers may be Accession Numbers, Order Numbers, Referral Request Identifiers, XDS Workflow Instance Identifiers, etc. Only Encounters on the ReferenceIdList are conveyed here, while other identifiers on that list are conveyed via Reference(Encounter | EpisodeOfCare | NlcoreEncounter) Constraints
| |||
event | 0..* | CodeableConcept | Element idDocumentReference.context.eventShort description EventCodeList DefinitionThis list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. An event can further specialize the act inherent in the type, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more event codes are included, they shall not conflict with the values inherent in the class or type elements as such a conflict would create an ambiguous situation. Unordered, Open, by $this(Value) BindingThis list of codes represents the main clinical acts being documented.
| |||
procedureAnatomicalLocation | 0..1 | NlcoreAnatomicalLocationBinding | Element idDocumentReference.context.event:procedureAnatomicalLocationShort description ProcedureAnatomicalLocation / Location Alternate namesLocatie, nl-core-AnatomicalLocation, VerrichtingAnatomischeLocatie DefinitionAnatomical location which is the focus of the procedure. The value set is proposed by IHE MCWG and also suggested for the EU (Xt-EHR). The used value set is a subset of the value set defined in zib2020. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. This list of codes represents the main clinical acts being documented. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.event:procedureAnatomicalLocation.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.context.event:procedureAnatomicalLocation.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
laterality | C | 0..1 | Extension(CodeableConcept) | There are no (further) constraints on this element Element idDocumentReference.context.event:procedureAnatomicalLocation.extension:lateralityShort description Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. http://nictiz.nl/fhir/StructureDefinition/ext-AnatomicalLocation.Laterality ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.event:procedureAnatomicalLocation.extension:laterality.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.context.event:procedureAnatomicalLocation.extension:laterality.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idDocumentReference.context.event:procedureAnatomicalLocation.extension:laterality.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://nictiz.nl/fhir/StructureDefinition/ext-AnatomicalLocation.LateralityMappings
| |||
value[x] | 0..1 | Binding | Element idDocumentReference.context.event:procedureAnatomicalLocation.extension:laterality.value[x]Short description Laterality Alternate namesLateraliteit DefinitionLaterality adds information about body site to the anatomic location, e.g. left. LateraliteitCodelijst (required) Constraints
| |||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDocumentReference.context.event:procedureAnatomicalLocation.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
| ||
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.event:procedureAnatomicalLocation.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
modality | C | 0..* | CodeableConceptBinding | Element idDocumentReference.context.event:modalityShort description Modality Alternate namesModaliteit DefinitionType of medical imaging device, process or method that originally acquired or produced the data used to create the image or series of images, such as a CT scanner or MRI machine. For an image or series of images the modalities SHALL be specified. This list of codes represents the main clinical acts being documented. The cardinality or value of this element may be affected by these constraints: bbs-DocumentReference-2 Constraints
| ||
period | S Σ | 1..1 | Period | There are no (further) constraints on this element Element idDocumentReference.context.periodShort description Time of service that is being documented DefinitionThe time period over which the service that is described by the document was provided.
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.period.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.context.period.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
start | Σ C | 1..1 | dateTime | Element idDocumentReference.context.period.startShort description ProcedureStartDate / ServiceStartTime Alternate namesVerrichtingStartDatum Definition
If the low element is missing, the meaning is that the low boundary is not known. The cardinality or value of this element may be affected by these constraints: per-1 Constraints
| ||
end | Σ C | 0..1 | dateTime | Element idDocumentReference.context.period.endShort description ProcedureEndDate / ServiceStopTime Alternate namesVerrichtingEindDatum Definition
The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03. If the end of the period is missing, it means that the period is ongoing The cardinality or value of this element may be affected by these constraints: per-1 Constraints
| ||
facilityType | S | 1..1 | CodeableConceptBinding | Element idDocumentReference.context.facilityTypeShort description OrganizationType / HealthcareFacilityTypeCode Alternate namesOrganisatieType Definition
XDS Facility Type. OrganisatieTypeCodelijst (extensible) Constraints
| ||
practiceSetting | S | 1..1 | CodeableConceptBinding | Element idDocumentReference.context.practiceSettingShort description DepartmentSpecialty / PracticeSettingCode Alternate namesAfdelingSpecialisme Definition
This is an important piece of metadata that providers often rely upon to quickly sort and/or filter out to find specific content. This element should be based on a coarse classification system for the class of specialty practice. Recommend the use of the classification system for Practice Setting, such as that described by the Subject Matter Domain in LOINC. Additional details about where the content was created (e.g. clinical specialty). PracticeSettingCodeMCWG (required) Constraints
| ||
sourcePatientInfo | S | 1..1 | Reference(Patient | NlcorePatient) | Element idDocumentReference.context.sourcePatientInfoShort description SourcePatientId / SourcePatientInfo Definition
Reference(Patient | NlcorePatient) Allowed aggregation:contained Constraints
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.sourcePatientInfo.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.context.sourcePatientInfo.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
reference | Σ C | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.sourcePatientInfo.referenceShort description Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. The cardinality or value of this element may be affected by these constraints: ref-1 Constraints
| ||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element idDocumentReference.context.sourcePatientInfo.typeShort description Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
| ||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idDocumentReference.context.sourcePatientInfo.identifierShort description Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| ||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.sourcePatientInfo.displayShort description Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| ||
related | 0..* | Reference(Resource) | Element idDocumentReference.context.relatedShort description ReferenceIdList DefinitionA list of identifiers that apply to the document. Identifiers may be Accession Numbers, Order Numbers, Referral Request Identifiers, XDS Workflow Instance Identifiers, etc. For Imaging (Reports), use the Accession Number with Assigning Authority, Order Number with Assigning Authority and StudyUID, as proposed by the IHE MCWG to support linking the Images and Reports together. Encounters on the ReferenceIdList are conveyed via Unordered, Open, by identifier.type(Value) Constraints
| |||
accessionNumber | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumberShort description Related identifiers or resources DefinitionRelated identifiers or resources associated with the DocumentReference. May be identifiers or resources that caused the DocumentReference or referenced Document to be created.
| |||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
reference | Σ C | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.referenceShort description Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. The cardinality or value of this element may be affected by these constraints: ref-1 Constraints
| ||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.typeShort description Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
| ||
identifier | Σ | 1..1 | Identifier | Element idDocumentReference.context.related:accessionNumber.identifierShort description AccessionNumber Alternate namesAccessionNumber DefinitionA locally unique record number in the RIS that identifies the imaging procedure request. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.identifier.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.identifier.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.identifier.useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
type | Σ | 1..1 | CodeableConceptBindingPattern | Element idDocumentReference.context.related:accessionNumber.identifier.typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
{ "coding": [ { "system": "urn:ietf:rfc:3986", "code": "urn:ihe:iti:xds:2013:accession" } ] }Mappings
| ||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.identifier.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patientMappings
| ||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.identifier.valueShort description The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.identifier.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
assigner | Σ | 0..1 | Reference(Organization | NlcoreHealthcareProviderOrganization) | Element idDocumentReference.context.related:accessionNumber.identifier.assignerShort description Organization that issued id (may be just text) DefinitionIssuer of Accession Number. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(Organization | NlcoreHealthcareProviderOrganization) Constraints
| ||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.related:accessionNumber.displayShort description Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| ||
studyInstanceUID | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUIDShort description Related identifiers or resources DefinitionRelated identifiers or resources associated with the DocumentReference. May be identifiers or resources that caused the DocumentReference or referenced Document to be created.
| |||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
reference | Σ C | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.referenceShort description Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. The cardinality or value of this element may be affected by these constraints: ref-1 Constraints
| ||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.typeShort description Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
| ||
identifier | Σ | 1..1 | Identifier | Element idDocumentReference.context.related:studyInstanceUID.identifierShort description StudyInstanceUID Alternate namesStudyInstanceUID DefinitionThe globally unique DICOM identifier of the imaging study upon which the imaging report is based, assigned by the modality or PACS. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| ||
id | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.identifier.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.identifier.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
| ||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.identifier.useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
type | Σ | 1..1 | CodeableConceptBindingPattern | Element idDocumentReference.context.related:studyInstanceUID.identifier.typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
{ "coding": [ { "system": "urn:ietf:rfc:3986", "code": "urn:ihe:iti:xds:2016:studyInstanceUID" } ] }Mappings
| ||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.identifier.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patientMappings
| ||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.identifier.valueShort description The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.identifier.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.identifier.assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.context.related:studyInstanceUID.displayShort description Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
Note:
- The Nictiz Profiling Guidelines for FHIR R4 have been used as guidelines for creating the profile.
- The (element) descriptions present in het profile are taken (and translated, if necessary) from the respective dataset the mapped concept originates from. If concepts of different datasets are mapped to the same element within the profile, both descriptions have been included.
- The 'open world' modeling approach is adopted as much as possible. Notable exceptions are cardinalities that have been restricted based on the functional dataset of the MedMij use case, such as the minimum cardinalities of
.date
and.content.attachment.title
. - For the ValueSets bound in the profile, the following approach has been followed:
- If the IHE.MHD profile defines a ValueSet with a required binding on a certain element, those ValueSet and binding are kept as-is. Moreover, the terminology linked to the corresponding concept from the Nictiz BBS dataset or National IHE MetaData Set is added as an additional binding (assuming that the value set linked in the respective dataset is a subset of the ValueSet bound in the IHE.MHD profile);
- If a concept from the Nictiz BBS dataset is mapped on a certain element, and a value set is linked to that concept, the corresponding ValueSet is bound on that element, together with the binding specified in the dataset;
- If no concept from the Nictiz BBS dataset is mapped on a certain element, but there is a concept from the National IHE MetaData Set mapped to that element, and a value set is linked to that concept, the corresponding ValueSet is adopted on that element with an extensible binding.
3.1.2. Other profiles
FHIR R4 conformance resources developed by Nictiz (based on zib publication 2020) from the nl-core 0.12.0-beta.1 package are used and referenced where possible. In particular, the nl-core profiles the table below are used.
Zib | FHIR resource/data type | FHIR profile |
---|---|---|
Patient | Patient | nl-core-Patient |
HealthProfessional | PractitionerRole | nl-core-HealthProfessional-PractitionerRole |
HealthcareProvider | Organization | nl-core-HealthcareProvider-Organization |
Encounter | Encounter | nl-core-Encounter |
AnatomicalLocation | CodeableConcept | nl-core-AnatomicalLocation |
Table 1: Relevant nl-core profiles