3.2. FHIR profiles
3.2.1. Provider task-specific profiles
The following FHIR profiles have been introduced for the Provider Task standard:
| CIM (concept) | FHIR resource | FHIR profile |
|---|---|---|
| Task | Task | pt-Task |
| Activity | ActivityDefinition | pt-ActivityDefinition |
| ServiceRequest | ServiceRequestExecutionOrder | pt-ServiceRequestExecutionOrder |
| ServiceRequestDigitalGroupPlan | pt-ServiceRequestDigitalGroupPlan | |
| Endpoint | pt-Endpoint |
Table 1: Relevant Provider task-specific profiles
Note the following:
- The Nictiz Profiling Guidelines for FHIR R4 have been used as guidelines for creating the profiles.
- The (element) descriptions present in the profiles are taken from the respective Logical Model the mapped concept originates from.
- 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 several minimum cardinalities.
3.2.2. Other profiles
FHIR R4 conformance resources developed by Nictiz (based on zib publication 2020) from the nl-core 0.12.0-beta.4 package are used and referenced where possible. In particular, the zibs and corresponding nl-core profiles collected in the table below are used.
| Zib | FHIR resource | FHIR profile |
|---|---|---|
| Patient | Patient | nl-core-Patient |
| HealthProfessional | PractitionerRole Practitioner |
nl-core-HealthProfessional-PractitionerRole nl-core-HealthProfessional-Practitioner |
| HealthcareProvider | Location Organization |
nl-core-HealthcareProvider nl-core-HealthcareProvider-Organization |
Table 2: Relevant nl-core profiles
Note the following:
- 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 where relevant, 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 instead. However, since this should be the exception, the nl-core-HealthProfessional-Practitioner profile is never explicitly mentioned as a target profile. This is in line with the Nictiz Profiling Guidelines for FHIR R4.
3.2.1. Task
| PtTask (Task) | C | Task | |
| id | Σ | 0..1 | string |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| resource-origin | C | 0..1 | Extension(Reference(KT2_Device)) |
| instantiates | C | 0..* | Extension(Reference(KT2_ActivityDefinition)) |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | 1..* | Identifier | |
| instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) |
| instantiatesUri | Σ | 0..1 | uri |
| basedOn | Σ C | 0..* | Reference(PtServiceRequestDigitalGroupPlan) |
| groupIdentifier | Σ | 0..1 | Identifier |
| partOf | Σ C | 0..* | Reference(PtTask) |
| status | Σ ?! | 1..1 | codeBinding |
| statusReason | Σ | 0..1 | CodeableConcept |
| businessStatus | Σ | 0..1 | CodeableConcept |
| intent | Σ | 1..1 | codeBinding |
| priority | 0..1 | codeBinding | |
| code | Σ | 0..1 | CodeableConcept |
| description | Σ | 0..1 | string |
| focus | Σ C | 0..1 | Reference(PtServiceRequestExecutionOrder) |
| for | Σ C | 1..1 | Reference(NlcorePatient) |
| encounter | Σ C | 0..1 | Reference(Encounter) |
| executionPeriod | Σ C | 0..1 | Period |
| authoredOn | C | 0..1 | dateTime |
| lastModified | Σ C | 0..1 | dateTime |
| requester | Σ C | 0..1 | Reference(Device | Organization | Practitioner | PractitionerRole | RelatedPerson | NlcoreHealthProfessionalPractitionerRole) |
| performerType | 0..* | CodeableConceptBinding | |
| owner | Σ C | 1..1 | Reference(CareTeam | Device | HealthcareService | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | NlcoreCareTeam | NlcoreContactPerson | NlcoreHealthProfessionalPractitionerRole | NlcorePatient) |
| location | Σ C | 0..1 | Reference(Location) |
| reasonCode | 0..1 | CodeableConcept | |
| reasonReference | C | 0..1 | Reference(Resource) |
| insurance | C | 0..* | Reference(ClaimResponse | Coverage) |
| note | 0..* | Annotation | |
| relevantHistory | C | 0..* | Reference(Provenance) |
| restriction | 0..1 | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| repetitions | 0..1 | positiveInt | |
| period | C | 0..1 | Period |
| recipient | C | 0..* | Reference(Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| input | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| type | 1..1 | CodeableConcept | |
| value[x] | 1..1 | ||
| valueAddress | Address | ||
| valueAge | Age | ||
| valueAnnotation | Annotation | ||
| valueAttachment | Attachment | ||
| valueBase64Binary | base64Binary | ||
| valueBoolean | boolean | ||
| valueCanonical | canonical | ||
| valueCode | code | ||
| valueCodeableConcept | CodeableConcept | ||
| valueCoding | Coding | ||
| valueContactDetail | ContactDetail | ||
| valueContactPoint | ContactPoint | ||
| valueContributor | Contributor | ||
| valueCount | Count | ||
| valueDataRequirement | DataRequirement | ||
| valueDate | date | ||
| valueDateTime | dateTime | ||
| valueDecimal | decimal | ||
| valueDistance | Distance | ||
| valueDosage | Dosage | ||
| valueDuration | Duration | ||
| valueExpression | Expression | ||
| valueHumanName | HumanName | ||
| valueId | id | ||
| valueIdentifier | Identifier | ||
| valueInstant | instant | ||
| valueInteger | integer | ||
| valueMarkdown | markdown | ||
| valueMeta | Meta | ||
| valueMoney | Money | ||
| valueOid | oid | ||
| valueParameterDefinition | ParameterDefinition | ||
| valuePeriod | Period | ||
| valuePositiveInt | positiveInt | ||
| valueQuantity | Quantity | ||
| valueRange | Range | ||
| valueRatio | Ratio | ||
| valueReference | Reference | ||
| valueRelatedArtifact | RelatedArtifact | ||
| valueSampledData | SampledData | ||
| valueSignature | Signature | ||
| valueString | string | ||
| valueTime | time | ||
| valueTiming | Timing | ||
| valueTriggerDefinition | TriggerDefinition | ||
| valueUnsignedInt | unsignedInt | ||
| valueUri | uri | ||
| valueUrl | url | ||
| valueUsageContext | UsageContext | ||
| valueUuid | uuid | ||
| output | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| type | 1..1 | CodeableConcept | |
| value[x] | 1..1 | ||
| valueAddress | Address | ||
| valueAge | Age | ||
| valueAnnotation | Annotation | ||
| valueAttachment | Attachment | ||
| valueBase64Binary | base64Binary | ||
| valueBoolean | boolean | ||
| valueCanonical | canonical | ||
| valueCode | code | ||
| valueCodeableConcept | CodeableConcept | ||
| valueCoding | Coding | ||
| valueContactDetail | ContactDetail | ||
| valueContactPoint | ContactPoint | ||
| valueContributor | Contributor | ||
| valueCount | Count | ||
| valueDataRequirement | DataRequirement | ||
| valueDate | date | ||
| valueDateTime | dateTime | ||
| valueDecimal | decimal | ||
| valueDistance | Distance | ||
| valueDosage | Dosage | ||
| valueDuration | Duration | ||
| valueExpression | Expression | ||
| valueHumanName | HumanName | ||
| valueId | id | ||
| valueIdentifier | Identifier | ||
| valueInstant | instant | ||
| valueInteger | integer | ||
| valueMarkdown | markdown | ||
| valueMeta | Meta | ||
| valueMoney | Money | ||
| valueOid | oid | ||
| valueParameterDefinition | ParameterDefinition | ||
| valuePeriod | Period | ||
| valuePositiveInt | positiveInt | ||
| valueQuantity | Quantity | ||
| valueRange | Range | ||
| valueRatio | Ratio | ||
| valueReference | Reference | ||
| valueRelatedArtifact | RelatedArtifact | ||
| valueSampledData | SampledData | ||
| valueSignature | Signature | ||
| valueString | string | ||
| valueTime | time | ||
| valueTiming | Timing | ||
| valueTriggerDefinition | TriggerDefinition | ||
| valueUnsignedInt | unsignedInt | ||
| valueUri | uri | ||
| valueUrl | url | ||
| valueUsageContext | UsageContext | ||
| valueUuid | uuid |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This (FHIR) Task profile describes a patient-specific actionable item, intended to be presented to the patient in a client application (e.g., a PGO) and/or processed within the Koppeltaal workflow. It may optionally reference an ActivityDefinition that defines what should be launched or performed (module, questionnaire, information, measurement)." />
<purpose value="This profile represents a patient-specific actionable item, intended to be presented to the patient in a client application (e.g., a PGO) and/or processed in the Koppeltaal workflow, optionally instantiating an ActivityDefinition that can be launched or performed (module, questionnaire, information, measurement)." />
<copyright value="Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise." />
</mapping>
<definition value="A patient-specific actionable item, assigned to the patient and optionally linked to an ActivityDefinition describing what to launch or perform." />
</mapping>
</element>
</discriminator>
</slicing>
<definition value="A link to the ActivityDefinition that defines the launchable eHealth activity (i.e., what module/content should be launched or performed) associated with this Task. In both MedMij and Koppeltaal implementations, this link is carried using the Koppeltaal instantiates extension." />
</element>
</element>
</discriminator>
</slicing>
</element>
</type>
</element>
</type>
</element>
</type>
</mapping>
</element>
</element>
<definition value="Reference to the ServiceRequest that initiates the digital group plan for the patient. This is the module-level order and links the Task to the requested digital group plan." />
<targetProfile value="http://medmij.nl/fhir/StructureDefinition/pt-ServiceRequest-DigitalGroupPlan" />
</type>
</mapping>
</element>
</type>
</element>
<definition value="Current state of the Task in the workflow (e.g., requested, received, accepted, in-progress, completed, cancelled)." />
</mapping>
</element>
<definition value="Indicates how urgent it is to perform the activity (e.g., routine, urgent, asap)." />
</mapping>
</element>
<definition value="A free-text description of what is to be performed. Implementers should ensure the text is readable on mobile applications." />
</mapping>
</element>
<definition value="Reference to the ServiceRequest that contains patient-specific scheduling and/or instructions that deviate from or complement the generic ActivityDefinition guidance." />
<targetProfile value="http://medmij.nl/fhir/StructureDefinition/pt-ServiceRequest-ExecutionOrder" />
</type>
</element>
<definition value="The patient who benefits from the performance of the service specified in the task." />
<comment value="In this profile, this element always refers to the patient for whom the task is intended." />
<requirements value="Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively). This can also affect access control." />
</type>
</element>
<definition value="Time window in which the task should be performed (start/end), if applicable." />
</mapping>
</element>
<definition value="In Koppeltaal this element contains a reference to the person requesting the eHealth Task" />
<comment value="Each occurrence of the zib HealthProfessional is normally represented by _two_ FHIR resources: a PractitionerRole resource (instance of [nl-core-HealthProfessional-PractitionerRole](http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole)) and a Practitioner resource (instance of [nl-core-HealthProfessional-Practitioner](http://nictiz.nl/fhir/StructureDefinition/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.\n\nIn 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." />
<targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole" />
</type>
</mapping>
</element>
<definition value="Practitioner, CareTeam, RelatedPerson or Patient currently responsible for task execution." />
<comment value="For Koppeltaal: In Koppeltaal the patient is usually the person who executes the task. Note, this element is not intended to be used for access restriction. That is left to the relevant applications.\n\nEach occurrence of the zib HealthProfessional is normally represented by two FHIR resources: a PractitionerRole resource (instance of [nl-core-HealthProfessional-PractitionerRole](http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole)) and a Practitioner resource (instance of [nl-core-HealthProfessional-Practitioner](http://nictiz.nl/fhir/StructureDefinition/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.\n\nIn 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.\n\n In ProviderTasks, the owner is typically the performer of the task (usually the patient), but execution may also be delegated to another responsible party such as a caregiver/contact person or a care team." />
<targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole" />
</type>
</element>
</differential>
</StructureDefinition>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This (FHIR) Task profile describes a patient-specific actionable item, intended to be presented to the patient in a client application (e.g., a PGO) and/or processed within the Koppeltaal workflow. It may optionally reference an ActivityDefinition that defines what should be launched or performed (module, questionnaire, information, measurement).",
"purpose": "This profile represents a patient-specific actionable item, intended to be presented to the patient in a client application (e.g., a PGO) and/or processed in the Koppeltaal workflow, optionally instantiating an ActivityDefinition that can be launched or performed (module, questionnaire, information, measurement).",
"copyright": "Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise.",
{
}
],
{
"definition": "A patient-specific actionable item, assigned to the patient and optionally linked to an ActivityDefinition describing what to launch or perform.",
"Taak"
],
]
},
{
},
"definition": "A link to the ActivityDefinition that defines the launchable eHealth activity (i.e., what module/content should be launched or performed) associated with this Task. In both MedMij and Koppeltaal implementations, this link is carried using the Koppeltaal instantiates extension.",
"DigitaleActiviteit",
"user content"
]
},
{
},
{
}
},
{
{
"http://medmij.nl/fhir/StructureDefinition/pt-ActivityDefinition"
]
}
]
},
{
{
}
]
},
{
],
{
}
]
},
{
},
{
"definition": "Reference to the ServiceRequest that initiates the digital group plan for the patient. This is the module-level order and links the Task to the requested digital group plan.",
"GebaseerdOp"
],
{
"http://medmij.nl/fhir/StructureDefinition/pt-ServiceRequest-DigitalGroupPlan"
]
}
],
]
},
{
]
},
{
"definition": "Current state of the Task in the workflow (e.g., requested, received, accepted, in-progress, completed, cancelled).",
"Status"
],
]
},
{
"Prioriteit"
],
]
},
{
"definition": "A free-text description of what is to be performed. Implementers should ensure the text is readable on mobile applications.",
"Omschrijving"
],
{
}
]
},
{
"definition": "Reference to the ServiceRequest that contains patient-specific scheduling and/or instructions that deviate from or complement the generic ActivityDefinition guidance.",
{
"http://medmij.nl/fhir/StructureDefinition/pt-ServiceRequest-ExecutionOrder"
]
}
]
},
{
"definition": "The patient who benefits from the performance of the service specified in the task.",
"comment": "In this profile, this element always refers to the patient for whom the task is intended.",
"requirements": "Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively). This can also affect access control.",
{
"http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient"
]
}
]
},
{
"Periode"
],
{
}
]
},
{
"definition": "In Koppeltaal this element contains a reference to the person requesting the eHealth Task",
"comment": "Each occurrence of the zib HealthProfessional is normally represented by _two_ FHIR resources: a PractitionerRole resource (instance of [nl-core-HealthProfessional-PractitionerRole](http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole)) and a Practitioner resource (instance of [nl-core-HealthProfessional-Practitioner](http://nictiz.nl/fhir/StructureDefinition/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.\n\nIn 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.",
"Aanvrager"
],
{
"http://hl7.org/fhir/StructureDefinition/Device",
"http://hl7.org/fhir/StructureDefinition/Organization",
"http://hl7.org/fhir/StructureDefinition/Practitioner",
"http://hl7.org/fhir/StructureDefinition/PractitionerRole",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson",
"http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole"
]
}
],
]
},
{
"definition": "Practitioner, CareTeam, RelatedPerson or Patient currently responsible for task execution.",
"comment": "For Koppeltaal: In Koppeltaal the patient is usually the person who executes the task. Note, this element is not intended to be used for access restriction. That is left to the relevant applications.\n\nEach occurrence of the zib HealthProfessional is normally represented by two FHIR resources: a PractitionerRole resource (instance of [nl-core-HealthProfessional-PractitionerRole](http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole)) and a Practitioner resource (instance of [nl-core-HealthProfessional-Practitioner](http://nictiz.nl/fhir/StructureDefinition/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.\n\nIn 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.\n\n In ProviderTasks, the owner is typically the performer of the task (usually the patient), but execution may also be delegated to another responsible party such as a caregiver/contact person or a care team.",
{
"http://hl7.org/fhir/StructureDefinition/Practitioner",
"http://hl7.org/fhir/StructureDefinition/PractitionerRole",
"http://hl7.org/fhir/StructureDefinition/Organization",
"http://hl7.org/fhir/StructureDefinition/CareTeam",
"http://hl7.org/fhir/StructureDefinition/HealthcareService",
"http://hl7.org/fhir/StructureDefinition/Patient",
"http://hl7.org/fhir/StructureDefinition/Device",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson",
"http://nictiz.nl/fhir/StructureDefinition/nl-core-CareTeam",
"http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient",
"http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole",
"http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactPerson"
]
}
]
}
]
}
}
3.2.2. ActivityDefinition
| PtActivityDefinition (ActivityDefinition) | C | ActivityDefinition | |
| id | Σ | 0..1 | string |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 1..* | Extension |
| resource-origin | C | 0..1 | Extension(Reference(KT2_Device)) |
| endpoint | C | 1..* | Extension(Reference(KT2_Endpoint)) |
| publisherId | C | 0..1 | Extension(id) |
| modifierExtension | ?! C | 0..* | Extension |
| url | Σ | 1..1 | uri |
| identifier | Σ | 0..* | Identifier |
| version | Σ | 0..1 | string |
| name | Σ C | 0..1 | string |
| title | Σ | 1..1 | string |
| subtitle | 0..1 | string | |
| status | Σ ?! | 1..1 | codeBinding |
| experimental | Σ | 0..1 | boolean |
| subject[x] | 0..1 | Binding | |
| subjectCodeableConcept | CodeableConcept | ||
| subjectReference | Reference(Group) | ||
| date | Σ | 0..1 | dateTime |
| publisher | Σ | 0..1 | string |
| contact | Σ | 0..* | ContactDetail |
| description | Σ | 0..1 | markdown |
| useContext | Σ | 0..* | UsageContext |
| jurisdiction | Σ | 0..* | CodeableConceptBinding |
| purpose | 0..1 | markdown | |
| usage | 0..1 | string | |
| copyright | 0..1 | markdown | |
| approvalDate | 0..1 | date | |
| lastReviewDate | 0..1 | date | |
| effectivePeriod | Σ C | 0..1 | Period |
| topic | 0..* | CodeableConceptBinding | |
| author | 0..* | ContactDetail | |
| editor | 0..* | ContactDetail | |
| reviewer | 0..* | ContactDetail | |
| endorser | 0..* | ContactDetail | |
| relatedArtifact | 0..* | RelatedArtifact | |
| library | 0..* | canonical(Library) | |
| kind | Σ | 0..1 | codeBinding |
| profile | 0..1 | canonical(StructureDefinition) | |
| code | Σ | 0..1 | CodeableConcept |
| intent | 0..1 | codeBinding | |
| priority | 0..1 | codeBinding | |
| doNotPerform | Σ ?! | 0..1 | boolean |
| timing[x] | 0..1 | ||
| timingTiming | Timing | ||
| location | C | 0..1 | Reference(Location) |
| participant | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| type | 1..1 | codeBinding | |
| role | 0..1 | CodeableConcept | |
| product[x] | 0..1 | ||
| productCodeableConcept | CodeableConcept | ||
| productReference | Reference(Medication | Substance) | ||
| quantity | C | 0..1 | SimpleQuantity |
| dosage | 0..* | Dosage | |
| bodySite | 0..* | CodeableConcept | |
| specimenRequirement | C | 0..* | Reference(SpecimenDefinition) |
| observationRequirement | C | 0..* | Reference(ObservationDefinition) |
| observationResultRequirement | C | 0..* | Reference(ObservationDefinition) |
| transform | 0..1 | canonical(StructureMap) | |
| dynamicValue | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| path | 1..1 | string | |
| expression | C | 1..1 | Expression |
</telecom>
</contact>
<description value="This (FHIR) ActivityDefinition profile describes a reusable definition of a launchable digital (eHealth) activity that can be requested for a patient in MedMij and/or Koppeltaal workflows. It captures the clinical intent and the technical launch information (e.g., endpoint)." />
<copyright value="Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise." />
</mapping>
<definition value="Definition of a launchable digital (eHealth) activity that can be used as a template for patient-specific workflow requests. The definition may describe different activity types (e.g., launching a third-party module, presenting information, completing a questionnaire, or performing a measurement) and includes the technical launch details needed to invoke the activity in the correct context." />
</mapping>
</element>
</discriminator>
</slicing>
</element>
</type>
</element>
<definition value="Mandatory reference to the service application (endpoint) that provides the launchable eHealth activity. Can be more than one endpoint." />
</type>
</element>
</type>
</element>
</element>
</mapping>
</element>
<definition value="Lifecycle status of the digital activity (e.g., draft, active, retired). A retired activity can no longer be selected or assigned." />
</mapping>
</element>
<definition value="Organization responsible for the content/functionality of this digital activity and its maintenance." />
</mapping>
</element>
</mapping>
</element>
</element>
<definition value="A detailed description of how the activity definition is used from a clinical perspective. In the MedMij use case, this text is intended for the healthcare professional who is selecting and assigning the activity to the patient." />
</element>
<definition value="Descriptive topics related to the content of the activity. The topic is used to indicate that the activity is intended or suitable for initialization by patients." />
<description value="High-level categorization of the definition, used for indicating special patient initialised activities" />
</binding>
</element>
<definition value="Generic recommendation for how often/when the activity is typically performed. Patient-specific scheduling belongs in the clinical order (e.g., ServiceRequestExecutionOrder)." />
</type>
</mapping>
</element>
</differential>
</StructureDefinition>
{
{
}
],
"description": "This (FHIR) ActivityDefinition profile describes a reusable definition of a launchable digital (eHealth) activity that can be requested for a patient in MedMij and/or Koppeltaal workflows. It captures the clinical intent and the technical launch information (e.g., endpoint).",
"copyright": "Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise.",
{
}
],
{
"definition": "Definition of a launchable digital (eHealth) activity that can be used as a template for patient-specific workflow requests. The definition may describe different activity types (e.g., launching a third-party module, presenting information, completing a questionnaire, or performing a measurement) and includes the technical launch details needed to invoke the activity in the correct context.",
"Digitale Activiteit"
],
]
},
{
},
},
{
{
}
]
},
{
"definition": "Mandatory reference to the service application (endpoint) that provides the launchable eHealth activity. Can be more than one endpoint.",
{
"http://koppeltaal.nl/fhir/StructureDefinition/KT2EndpointExtension"
]
}
]
},
{
{
}
]
},
{
},
{
"Titel"
],
]
},
{
"definition": "Lifecycle status of the digital activity (e.g., draft, active, retired). A retired activity can no longer be selected or assigned.",
"Status"
],
]
},
{
"definition": "Organization responsible for the content/functionality of this digital activity and its maintenance.",
{
}
]
},
{
"Omschrijving"
],
{
}
]
},
{
},
{
"definition": "A detailed description of how the activity definition is used from a clinical perspective. In the MedMij use case, this text is intended for the healthcare professional who is selecting and assigning the activity to the patient."
},
{
"definition": "Descriptive topics related to the content of the activity. The topic is used to indicate that the activity is intended or suitable for initialization by patients.",
"description": "High-level categorization of the definition, used for indicating special patient initialised activities",
}
},
{
"definition": "Generic recommendation for how often/when the activity is typically performed. Patient-specific scheduling belongs in the clinical order (e.g., ServiceRequestExecutionOrder).",
"Tijdschema"
],
],
]
}
]
}
}
3.2.3. Endpoint
| PtEndpoint (Endpoint) | C | Endpoint | |
| id | Σ | 0..1 | string |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| resource-origin | C | 0..1 | Extension(Reference(KT2_Device)) |
| clientId | C | 0..1 | Extension(string) |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | Σ | 0..* | Identifier |
| status | Σ ?! | 1..1 | codeBinding |
| connectionType | Σ | 1..1 | CodingBinding |
| name | Σ | 0..1 | string |
| managingOrganization | Σ C | 0..1 | Reference(Organization | NlcoreHealthcareProviderOrganization) |
| contact | C | 0..* | ContactPoint |
| period | Σ C | 0..1 | Period |
| payloadType | Σ | 1..* | CodeableConcept |
| payloadMimeType | Σ | 0..* | codeBinding |
| address | Σ | 1..1 | url |
| header | 0..* | string |
</telecom>
</contact>
<description value="This (FHIR) Endpoint profile represents the technical FHIR REST endpoint of a source system (XIS), used by a ProviderTask to retrieve and update task data and the required context for the ProviderTask use case." />
</discriminator>
</slicing>
</element>
</type>
</element>
</type>
</element>
</binding>
</element>
<targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization" />
</type>
</element>
</differential>
</StructureDefinition>
{
{
}
],
"description": "This (FHIR) Endpoint profile represents the technical FHIR REST endpoint of a source system (XIS), used by a ProviderTask to retrieve and update task data and the required context for the ProviderTask use case.",
{
}
},
{
{
}
]
},
{
]
},
{
}
},
{
{
"http://hl7.org/fhir/StructureDefinition/Organization",
"http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization"
]
}
]
}
]
}
}
3.2.4. ServiceRequestExecutionOrder
| PtServiceRequestExecutionOrder (ServiceRequest) | C | ServiceRequest | |
| id | Σ | 0..1 | string |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| resource-origin | C | 0..1 | Extension(Reference(KT2_Device)) |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | Σ | 0..* | Identifier |
| instantiatesCanonical | Σ | 0..* | canonical(ActivityDefinition | PlanDefinition) |
| instantiatesUri | Σ | 0..* | uri |
| basedOn | Σ C | 0..* | Reference(CarePlan | MedicationRequest | ServiceRequest) |
| replaces | Σ C | 0..* | Reference(ServiceRequest) |
| requisition | Σ | 0..1 | Identifier |
| status | Σ ?! | 1..1 | codeBinding |
| intent | Σ ?! | 1..1 | codeBindingPattern |
| category | Σ | 0..* | CodeableConcept |
| priority | Σ | 0..1 | codeBinding |
| doNotPerform | Σ ?! | 0..1 | boolean |
| code | Σ | 0..1 | CodeableConcept |
| orderDetail | Σ C | 0..* | CodeableConcept |
| quantity[x] | Σ | 0..1 | |
| quantityQuantity | Quantity | ||
| quantityRange | Range | ||
| quantityRatio | Ratio | ||
| subject | Σ C | 1..1 | Reference(Device | Group | Location | Patient | NlcorePatient) |
| encounter | Σ C | 0..1 | Reference(Encounter) |
| occurrence[x] | Σ | 0..1 | |
| occurrenceDateTime | dateTime | ||
| occurrencePeriod | Period | ||
| occurrenceTiming | Timing | ||
| asNeeded[x] | Σ | 0..1 | |
| asNeededBoolean | boolean | ||
| asNeededCodeableConcept | CodeableConcept | ||
| authoredOn | Σ | 0..1 | dateTime |
| requester | Σ C | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | NlcoreHealthProfessionalPractitionerRole) |
| performerType | Σ | 0..1 | CodeableConcept |
| performer | Σ C | 0..* | Reference(CareTeam | Device | HealthcareService | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| locationCode | Σ | 0..* | CodeableConcept |
| locationReference | Σ C | 0..* | Reference(Location) |
| reasonCode | Σ | 0..* | CodeableConcept |
| reasonReference | Σ C | 0..* | Reference(Condition | DiagnosticReport | DocumentReference | Observation) |
| insurance | C | 0..* | Reference(ClaimResponse | Coverage) |
| supportingInfo | C | 0..* | Reference(Resource) |
| specimen | Σ C | 0..* | Reference(Specimen) |
| bodySite | Σ | 0..* | CodeableConcept |
| note | 0..* | Annotation | |
| patientInstruction | Σ | 1..1 | string |
| relevantHistory | C | 0..* | Reference(Provenance) |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="Patient-specific execution plan for a digital activity. This ServiceRequest captures patient-specific scheduling and instructions that deviate from or complement the generic ActivityDefinition. It is referenced from the patient-facing Task via `Task.focus`." />
<purpose value="To represent the healthcare professional’s order to start a specific digital activity for a patient." />
<copyright value="Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise." />
</mapping>
<definition value="Patient-specific execution plan for a digital activity, containing scheduling (occurrence) and patient instruction. It is referenced from Task via `Task.focus`." />
</mapping>
</element>
</discriminator>
</slicing>
</element>
</type>
</element>
</element>
</type>
</element>
<definition value="Requested schedule for performing the activity (e.g., duration, frequency, time of day)." />
</mapping>
</element>
<comment value="Each occurrence of the zib HealthProfessional is normally represented by _two_ FHIR resources: a PractitionerRole resource (instance of [nl-core-HealthProfessional-PractitionerRole](http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole)) and a Practitioner resource (instance of [nl-core-HealthProfessional-Practitioner](http://nictiz.nl/fhir/StructureDefinition/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.\n\nIn 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." />
<targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole" />
</type>
</mapping>
</element>
<definition value="Patient-oriented instructions that may differ from or add to the generic activity information (e.g., fasting measurements, preferred timing, preparation steps). These instructions should be shown alongside the Task(s) created from this order." />
</mapping>
</element>
</differential>
</StructureDefinition>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "Patient-specific execution plan for a digital activity. This ServiceRequest captures patient-specific scheduling and instructions that deviate from or complement the generic ActivityDefinition. It is referenced from the patient-facing Task via `Task.focus`.",
"purpose": "To represent the healthcare professional’s order to start a specific digital activity for a patient.",
"copyright": "Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise.",
{
}
],
{
"definition": "Patient-specific execution plan for a digital activity, containing scheduling (occurrence) and patient instruction. It is referenced from Task via `Task.focus`.",
"Uitvoeringsopdracht",
"referral",
"referral request",
"transfer of care request"
],
{
}
]
},
{
}
},
{
{
}
]
},
{
},
{
{
"http://hl7.org/fhir/StructureDefinition/Patient",
"http://hl7.org/fhir/StructureDefinition/Group",
"http://hl7.org/fhir/StructureDefinition/Location",
"http://hl7.org/fhir/StructureDefinition/Device",
"http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient"
]
}
]
},
{
"definition": "Requested schedule for performing the activity (e.g., duration, frequency, time of day).",
"Tijdschema"
],
{
}
]
},
{
"comment": "Each occurrence of the zib HealthProfessional is normally represented by _two_ FHIR resources: a PractitionerRole resource (instance of [nl-core-HealthProfessional-PractitionerRole](http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole)) and a Practitioner resource (instance of [nl-core-HealthProfessional-Practitioner](http://nictiz.nl/fhir/StructureDefinition/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.\n\nIn 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.",
"Aanvrager",
"orderer"
],
{
"http://hl7.org/fhir/StructureDefinition/Practitioner",
"http://hl7.org/fhir/StructureDefinition/PractitionerRole",
"http://hl7.org/fhir/StructureDefinition/Organization",
"http://hl7.org/fhir/StructureDefinition/Patient",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson",
"http://hl7.org/fhir/StructureDefinition/Device",
"http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole"
]
}
],
{
}
]
},
{
"definition": "Patient-oriented instructions that may differ from or add to the generic activity information (e.g., fasting measurements, preferred timing, preparation steps). These instructions should be shown alongside the Task(s) created from this order.",
"PatiëntenInstructie"
],
{
}
]
}
]
}
}
3.2.5. ServiceRequestDigitalGroupPlan
| PtServiceRequestDigitalGroupPlan (ServiceRequest) | C | ServiceRequest | |
| id | Σ | 0..1 | string |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| resource-origin | C | 0..1 | Extension(Reference(KT2_Device)) |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | Σ | 0..* | Identifier |
| instantiatesCanonical | Σ | 0..* | canonical(ActivityDefinition | PlanDefinition) |
| instantiatesUri | Σ | 0..* | uri |
| basedOn | Σ C | 0..* | Reference(CarePlan | MedicationRequest | ServiceRequest) |
| replaces | Σ C | 0..* | Reference(ServiceRequest) |
| requisition | Σ | 0..1 | Identifier |
| status | Σ ?! | 1..1 | codeBinding |
| intent | Σ ?! | 1..1 | codeBindingPattern |
| category | Σ | 0..* | CodeableConcept |
| priority | Σ | 0..1 | codeBinding |
| doNotPerform | Σ ?! | 0..1 | boolean |
| code | Σ | 1..1 | CodeableConcept |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | Σ | 0..* | Coding |
| text | Σ | 1..1 | string |
| orderDetail | Σ C | 0..* | CodeableConcept |
| quantity[x] | Σ | 0..1 | |
| quantityQuantity | Quantity | ||
| quantityRange | Range | ||
| quantityRatio | Ratio | ||
| subject | Σ C | 1..1 | Reference(Device | Group | Location | Patient | NlcorePatient) |
| encounter | Σ C | 0..1 | Reference(Encounter) |
| occurrence[x] | Σ | 0..1 | |
| occurrenceDateTime | dateTime | ||
| occurrencePeriod | Period | ||
| occurrenceTiming | Timing | ||
| asNeeded[x] | Σ | 0..1 | |
| asNeededBoolean | boolean | ||
| asNeededCodeableConcept | CodeableConcept | ||
| authoredOn | Σ | 0..1 | dateTime |
| requester | Σ C | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | NlcoreHealthProfessionalPractitionerRole) |
| performerType | Σ | 0..1 | CodeableConcept |
| performer | Σ C | 0..* | Reference(CareTeam | Device | HealthcareService | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| locationCode | Σ | 0..* | CodeableConcept |
| locationReference | Σ C | 0..* | Reference(Location) |
| reasonCode | Σ | 0..* | CodeableConcept |
| reasonReference | Σ C | 0..* | Reference(Condition | DiagnosticReport | DocumentReference | Observation) |
| insurance | C | 0..* | Reference(ClaimResponse | Coverage) |
| supportingInfo | C | 0..* | Reference(Resource) |
| specimen | Σ C | 0..* | Reference(Specimen) |
| bodySite | Σ | 0..* | CodeableConcept |
| note | 0..* | Annotation | |
| patientInstruction | Σ | 0..1 | string |
| relevantHistory | C | 0..* | Reference(Provenance) |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="Clinical request representing the selected digital group plan for a specific patient. This ServiceRequest identifies which digital group plan is requested. Patient-specific scheduling and instructions are provided in a separate ServiceRequest" />
<purpose value="To represent the healthcare professional’s order to start a specific digital group plan for a patient." />
<copyright value="Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise." />
<definition value="Patient-specific clinical order to initiate a digital group plan. It is referenced from the patient-facing Task via Task.basedOn." />
</element>
</discriminator>
</slicing>
</element>
</type>
</element>
</element>
<definition value="Identifies which digital group plan is requested for the patient. The human-readable (display) name of the digital group plan is carried in `code.text` and is used as the group label in the PHR." />
</element>
<definition value="Human-readable name of the digital group plan. This name is used as the display label of the Task group in the PHR and MUST match the name used to identify the group in the `Task.basedOn` reference. The source system fills this element with the (display) name of the digital group plan when a healthcare professional starts a digital group plan/module for a patient." />
</element>
</type>
</element>
<comment value="Each occurrence of the zib HealthProfessional is normally represented by _two_ FHIR resources: a PractitionerRole resource (instance of [nl-core-HealthProfessional-PractitionerRole](http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole)) and a Practitioner resource (instance of [nl-core-HealthProfessional-Practitioner](http://nictiz.nl/fhir/StructureDefinition/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.\n\nIn 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." />
<targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole" />
</type>
</element>
</differential>
</StructureDefinition>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "Clinical request representing the selected digital group plan for a specific patient. This ServiceRequest identifies which digital group plan is requested. Patient-specific scheduling and instructions are provided in a separate ServiceRequest",
"purpose": "To represent the healthcare professional’s order to start a specific digital group plan for a patient.",
"copyright": "Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise.",
{
"definition": "Patient-specific clinical order to initiate a digital group plan. It is referenced from the patient-facing Task via Task.basedOn.",
"Module-opdracht",
"referral",
"referral request",
"transfer of care request"
]
},
{
}
},
{
{
}
]
},
{
},
{
"definition": "Identifies which digital group plan is requested for the patient. The human-readable (display) name of the digital group plan is carried in `code.text` and is used as the group label in the PHR.",
"Identificatie digitaal groepsplan"
],
},
{
"definition": "Human-readable name of the digital group plan. This name is used as the display label of the Task group in the PHR and MUST match the name used to identify the group in the `Task.basedOn` reference. The source system fills this element with the (display) name of the digital group plan when a healthcare professional starts a digital group plan/module for a patient.",
"Naam digitaal groepsplan"
],
},
{
{
"http://hl7.org/fhir/StructureDefinition/Patient",
"http://hl7.org/fhir/StructureDefinition/Group",
"http://hl7.org/fhir/StructureDefinition/Location",
"http://hl7.org/fhir/StructureDefinition/Device",
"http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient"
]
}
]
},
{
"comment": "Each occurrence of the zib HealthProfessional is normally represented by _two_ FHIR resources: a PractitionerRole resource (instance of [nl-core-HealthProfessional-PractitionerRole](http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole)) and a Practitioner resource (instance of [nl-core-HealthProfessional-Practitioner](http://nictiz.nl/fhir/StructureDefinition/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.\n\nIn 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.",
{
"http://hl7.org/fhir/StructureDefinition/Practitioner",
"http://hl7.org/fhir/StructureDefinition/PractitionerRole",
"http://hl7.org/fhir/StructureDefinition/Organization",
"http://hl7.org/fhir/StructureDefinition/Patient",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson",
"http://hl7.org/fhir/StructureDefinition/Device",
"http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole"
]
}
]
}
]
}
}