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.

idΣ0..1id
id0..1string
extensionC0..*Extension
versionIdΣ0..1id
lastUpdatedΣ0..1instant
sourceΣ0..1uri
profileΣ0..*canonical(StructureDefinition)
securityΣ0..*CodingBinding
tagΣ0..*Coding
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionC0..*Extension
modifierExtension?! C0..0Extension
masterIdentifier1..1UniqueIdIdentifier
entryUUID0..*EntryUUIDIdentifier
statusΣ ?!1..1codeBindingPattern
docStatusΣ0..0codeBinding
typeS Σ1..1CodeableConceptBinding
id0..1string
extensionC0..*Extension
radiologyStudiesΣ1..1CodingPattern
imagesΣ C0..1CodingPattern
reportsΣ C0..1CodingPattern
textΣ0..1string
subjectS Σ1..1Reference(Patient | NlcorePatient)
dateS Σ1..1instant
locationS Σ1..1Reference(NlcoreHealthcareProviderOrganization)
performerS Σ0..1Reference(NlcoreHealthProfessionalPractitionerRole)
authenticator0..1Reference(Practitioner | PractitionerRole | Organization | NlcoreHealthProfessionalPractitionerRole | NlcoreHealthcareProviderOrganization)
custodian0..1Reference(Organization)
id0..1string
extensionC0..*Extension
modifierExtensionΣ ?! C0..*Extension
codeΣ1..1codeBinding
targetΣ1..1Reference(DocumentReference)
descriptionΣ0..1string
securityLabelS Σ1..*CodeableConceptBinding
id0..1string
extensionC0..*Extension
modifierExtensionΣ ?! C0..*Extension
id0..1string
extensionC0..*Extension
contentTypeΣ1..1codeBinding
languageS Σ1..1codeBinding
data0..0base64Binary
urlΣ1..1url
sizeΣ0..1unsignedInt
hashΣ0..1base64Binary
titleΣ1..1string
creationS Σ1..1dateTime
formatS Σ1..1CodingBinding
id0..1string
extensionC0..*Extension
modifierExtensionΣ ?! C0..*Extension
encounter0..*Reference(Encounter | EpisodeOfCare | NlcoreEncounter)
id0..1string
id0..1string
extensionC0..*Extension
url1..1uriFixed Value
valueCodeableConceptCodeableConcept
codingΣ0..*Coding
textΣ0..1string
modalityC0..*CodeableConceptBinding
id0..1string
extensionC0..*Extension
startΣ C1..1dateTime
endΣ C0..1dateTime
facilityTypeS1..1CodeableConceptBinding
practiceSettingS1..1CodeableConceptBinding
id0..1string
extensionC0..*Extension
referenceΣ C0..1string
typeΣ0..1uriBinding
identifierΣ0..1Identifier
displayΣ0..1string
id0..1string
extensionC0..*Extension
referenceΣ C0..1string
typeΣ0..1uriBinding
id0..1string
extensionC0..*Extension
useΣ ?!0..1codeBinding
typeΣ1..1CodeableConceptBindingPattern
systemΣ0..1uri
valueΣ1..1string
periodΣ0..1Period
assignerΣ0..1Reference(Organization | NlcoreHealthcareProviderOrganization)
displayΣ0..1string
id0..1string
extensionC0..*Extension
referenceΣ C0..1string
typeΣ0..1uriBinding
id0..1string
extensionC0..*Extension
useΣ ?!0..1codeBinding
typeΣ1..1CodeableConceptBindingPattern
systemΣ0..1uri
valueΣ1..1string
periodΣ0..1Period
assignerΣ0..1Reference(Organization)
displayΣ0..1string

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