<status value="draft" /> <publisher value="Nictiz" /> <contact> <name value="Nictiz" /> <telecom> <system value="url" /> <value value="https://www.nictiz.nl" /> <use value="work" /> </telecom> </contact> <description value="Therapeutic or diagnostic procedure the patient will undergo (the complementary profile [nl-core-Procedure-request](http://nictiz.nl/fhir/StructureDefinition/nl-core-Procedure-request) can be used for therapeutic or diagnostics procedures that the has undergone). A procedure can be a simple blood pressure measurement, but also a complex heart surgery. In some care settings, the term treatment is used instead of the term procedure." /> <purpose value="A derived profile from [zib-Procedure-ServiceRequest](http://nictiz.nl/fhir/StructureDefinition/zib-Procedure-request) to provide a version better suited for implementation purposes. This profile augments the base profile with elements found in the various use cases that have adopted the zib." /> <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." /> <fhirVersion value="4.0.1" /> <mapping> <identity value="zib-procedure-v5.2-2020EN" /> <uri value="https://zibs.nl/wiki/Procedure-v5.2(2020EN)" /> <name value="zib Procedure-v5.2(2020EN)" /> </mapping> <kind value="resource" /> <abstract value="false" /> <type value="ServiceRequest" /> <baseDefinition value="http://nictiz.nl/fhir/StructureDefinition/zib-Procedure-request" /> <derivation value="constraint" /> <differential> <element id="ServiceRequest"> <path value="ServiceRequest" /> <comment value="The zib Procedure is mapped both to this ServiceRequest profile and a profile on Procedure (<http://nictiz.nl/fhir/StructureDefinition/nl-core-Procedure-event>) to align with the intention of FHIR. All past procedures are covered using this Procedure resource, while all future procedures, including the advised procedures, are covered in the ServiceRequest resource. Both resources contain the zib mappings. The planned and performed procedures can be linked using `Procedure.basedOn`." /> <alias value="nl-core-Procedure-request" /> </element> <element id="ServiceRequest.subject"> <path value="ServiceRequest.subject" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Patient" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Group" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Location" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Device" /> <targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient" /> </type> </element> <element id="ServiceRequest.requester"> <path value="ServiceRequest.requester" /> <comment value="The zib mapping contains a known cardinality difference (`0..*` versus `0..1`). The zib will be aligned in a future version with the cardinality of FHIR, therefore this profile pre-adopts the `0..1` cardinality for the requester. 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. 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 zib-HealthProfessional-Practitioner profile is not explicitly mentioned as a target profile." /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Practitioner" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/PractitionerRole" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Organization" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Patient" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/RelatedPerson" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Device" /> <targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole" /> </type> </element> <element id="ServiceRequest.performer"> <path value="ServiceRequest.performer" /> <comment value="If multiple performers are present, it is interpreted as a list of *alternative* performers without any preference regardless of order. This deviates from the zib definition where multiple references to the zib Healthprofessional should be interpreted as all the performers of the procedure. If order of preference is needed use the [request-performerOrder extension](extension-request-performerorder.html). Use CareTeam to represent a group of performers (for example, Practitioner A *and* Practitioner B). 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. 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." /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Practitioner" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/PractitionerRole" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Organization" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/CareTeam" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/HealthcareService" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Patient" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Device" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/RelatedPerson" /> <targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole" /> <targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-CareTeam" /> </type> </element> <element id="ServiceRequest.locationReference"> <path value="ServiceRequest.locationReference" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Location" /> <targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider" /> </type> </element> <element id="ServiceRequest.reasonReference"> <path value="ServiceRequest.reasonReference" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Condition" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Observation" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/DocumentReference" /> <targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-Problem" /> </type> </element> <element id="ServiceRequest.bodySite"> <path value="ServiceRequest.bodySite" /> <type> <code value="CodeableConcept" /> <profile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-AnatomicalLocation" /> </type> </element> </differential> </StructureDefinition>

No narrative is provided for definitional resources. A human-readable rendering can be found in the implementation guide(s) where this resource is used.