Procedure Referral Information Model

DISCLAIMER: EVERYTHING ON THIS PAGE SHALL BE CONSIDERED DRAFT AS LONG AS THIS DISCLAIMER REMAINS PRESENT. - THIS PAGE IS ONGOING DISCUSSED DURING THE PROCEDURE REFERRAL WG.

This page describes the information model for a referral prescription (RP) Once this page is complete, it can be reworked as a FHIR logical datamodel artefact.
For some elements that are less self-evident in what FHIR resource they will be expressed, there is already a mention of the FHIR resource that might be used. As such, this page can already help define the scope of which FHIR artefacts need to be profiled.
The main FHIR resource for the prescription is expected to be the FHIR ServiceRequest.

• Common for all use cases:
  • 1..1 Patient SSIN identifier
  • 1..1 Prescriber NIHDI identifier
  • 1..1 Date creation
  • 0..* NIHDI identifiers of signing healthcare parties (for validity of the RP in certain cases) with dates
  • 1..* NIHDI identifiers that will perform the RP
  • 1..1 Period OR date for performing the RP
  • 1..1 Status with date
  • 1..1 Reference ID
  • 1..1 What is actually prescribed as a coded value (is this always possible?)
• Per use case:
  • 0..* Structured data linked to the specific model of RP
  • 0..* Not structured data linked to the specific model of RP
• Diagnostic imaging:
  • 0..* Questionnaire responses (FHIR QuestionnaireResponse - if this can be standardized, possibly also the FHIR Questionnaire )
  • 0..* Observations on the patients as coded values or free text
  • 0..* References to documents (FHIR DocumentReference)
• Physiotherapy:
• Nursing: