FHIR © HL7.org  |  Server Home  |  XIG Home  |  Server Source  |  FHIR  

FHIR IG Statistics: StructureDefinition/nl-core-Procedure-request

Packagenictiz.fhir.nl.r4.nl-core
TypeStructureDefinition
Idnl-core-Procedure-request
FHIR VersionR4
Sourcehttps://simplifier.net/resolve?scope=nictiz.fhir.nl.r4.nl-core@0.12.0-beta.1&canonical=http://nictiz.nl/fhir/StructureDefinition/nl-core-Procedure-request
URLhttp://nictiz.nl/fhir/StructureDefinition/nl-core-Procedure-request
Statusdraft
NameNlcoreProcedurerequest
Titlenl core Procedure request
Realmnl
DescriptionTherapeutic 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.
PurposeA 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.
CopyrightCopyright 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.
TypeServiceRequest
Kindresource

Resources that use this resource

StructureDefinition
nl-core-AbilityToPerformMouthcareActivities.Prosthesisnl core AbilityToPerformMouthcareActivities.Prosthesis
nl-core-HearingFunction.HearingAidnl core HearingFunction.HearingAid
nl-core-MedicalDevicenl core MedicalDevice
nl-core-Procedure-eventnl core Procedure event
nl-core-VisualFunction.VisualAidnl core VisualFunction.VisualAid
nl-core-Wound.Drainnl core Wound.Drain
palga-procedure-requestPalgaProcedureRequest
DentalCare-ProcedureEventDentalCare - Procedure Event Dental Care

Resources that this resource uses

StructureDefinition
nl-core-AnatomicalLocationnl core AnatomicalLocation
nl-core-CareTeamnl core CareTeam
nl-core-HealthProfessional-PractitionerRolenl core HealthProfessional PractitionerRole
nl-core-HealthcareProvidernl core HealthcareProvider
nl-core-Patientnl core Patient
nl-core-Problemnl core Problem
zib-Procedure-requestzib Procedure request

Narrative

Note: links and images are rebased to the (stated) source

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

Source

{
  "resourceType": "StructureDefinition",
  "id": "nl-core-Procedure-request",
  "text": {
    "status": "empty",
    "div": "<!-- snip (see above) -->"
  },
  "url": "http://nictiz.nl/fhir/StructureDefinition/nl-core-Procedure-request",
  "name": "NlcoreProcedurerequest",
  "title": "nl core Procedure request",
  "status": "draft",
  "publisher": "Nictiz",
  "contact": [
    {
      "name": "Nictiz",
      "telecom": [
        {
          "system": "url",
          "value": "https://www.nictiz.nl",
          "use": "work"
        }
      ]
    }
  ],
  "description": "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.\r\nIn some care settings, the term treatment is used instead of the term procedure.",
  "purpose": "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": "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": "4.0.1",
  "mapping": [
    {
      "identity": "zib-procedure-v5.2-2020EN",
      "uri": "https://zibs.nl/wiki/Procedure-v5.2(2020EN)",
      "name": "zib Procedure-v5.2(2020EN)"
    }
  ],
  "kind": "resource",
  "abstract": false,
  "type": "ServiceRequest",
  "baseDefinition": "http://nictiz.nl/fhir/StructureDefinition/zib-Procedure-request",
  "derivation": "constraint",
  "differential": {
    "element": [
      {
        "id": "ServiceRequest",
        "path": "ServiceRequest",
        "comment": "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.\r\n\r\nThe planned and performed procedures can be linked using `Procedure.basedOn`.",
        "alias": [
          "nl-core-Procedure-request"
        ]
      },
      {
        "id": "ServiceRequest.subject",
        "path": "ServiceRequest.subject",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "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"
            ]
          }
        ]
      },
      {
        "id": "ServiceRequest.requester",
        "path": "ServiceRequest.requester",
        "comment": "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.\r\n\r\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.\r\n\r\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 zib-HealthProfessional-Practitioner profile is not explicitly mentioned as a target profile.",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "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"
            ]
          }
        ]
      },
      {
        "id": "ServiceRequest.performer",
        "path": "ServiceRequest.performer",
        "comment": "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).\r\n\r\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.\r\n\r\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.",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "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-HealthProfessional-PractitionerRole",
              "http://nictiz.nl/fhir/StructureDefinition/nl-core-CareTeam"
            ]
          }
        ]
      },
      {
        "id": "ServiceRequest.locationReference",
        "path": "ServiceRequest.locationReference",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://hl7.org/fhir/StructureDefinition/Location",
              "http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider"
            ]
          }
        ]
      },
      {
        "id": "ServiceRequest.reasonReference",
        "path": "ServiceRequest.reasonReference",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://hl7.org/fhir/StructureDefinition/Condition",
              "http://hl7.org/fhir/StructureDefinition/Observation",
              "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
              "http://hl7.org/fhir/StructureDefinition/DocumentReference",
              "http://nictiz.nl/fhir/StructureDefinition/nl-core-Problem"
            ]
          }
        ]
      },
      {
        "id": "ServiceRequest.bodySite",
        "path": "ServiceRequest.bodySite",
        "type": [
          {
            "code": "CodeableConcept",
            "profile": [
              "http://nictiz.nl/fhir/StructureDefinition/nl-core-AnatomicalLocation"
            ]
          }
        ]
      }
    ]
  }
}