Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-27849

Appointment.patientInstructions from string to Codeable Concept

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      R4
    • Work Group:
      Patient Administration
    • Related Artifact(s):
      Appointment
    • Resolution Description:
      Hide

      Modify the datatype of the patientInstruction property from 

      string 0..1 to CodeableReference(DocumentReference, Binary, Communication) 0..*

      Which would then permit attaching multiple (often) pre-formatted documents for instructions in place of regular text, and still support plain text.

      Examples:

      // Text only
      <patientInstruction>
      <concept>
      <text value="blah blah"/>
      </concept>
      </patientInstruction>

      // Coded (with text)
      <patientInstruction>
      <concept>
      <coding>
      <system value="blah oid blah"/>
      <value value="blah"/>
      </coding>
      <text value="blah blah"/>
      </concept>
      </patientInstruction>

      // some attached document (DocumentReference, Binary, Communication?)
      <patientInstruction>
      <reference>
      <reference value="Binary/blah_pdf"/>
      <display value="blah blah"/>
      </reference>
      </patientInstruction>

       

      Show
      Modify the datatype of the patientInstruction property from  string 0..1 to CodeableReference(DocumentReference, Binary, Communication) 0.. * Which would then permit attaching multiple (often) pre-formatted documents for instructions in place of regular text, and still support plain text. Examples: // Text only <patientInstruction> <concept> <text value="blah blah"/> </concept> </patientInstruction> // Coded (with text) <patientInstruction> <concept> <coding> <system value="blah oid blah"/> <value value=" blah "/> </coding> <text value="blah blah"/> </concept> </patientInstruction> // some attached document (DocumentReference, Binary, Communication?) <patientInstruction> <reference> <reference value="Binary/blah_pdf"/> <display value="blah blah"/> </reference> </patientInstruction>  
    • Resolution Vote:
      Brian Postlethwaite/Simone Heckmann: 10-0-2
    • Change Category:
      Enhancement
    • Change Impact:
      Non-compatible

      Description

      Right now the Appointment.patientInstructions field is a string. I would like to propose updating it to a Codeable Concept or some other form where we can return multiple instructions, or multiple types of instructions.

      Our build allows for pre-appointment instructions and post-appointment instructions, as well as directions (how to get to a facility, etc.). We're going to have to concatenate all of those into a single string, which makes it difficult to display any time of complex instruction to a FHIR consumer.

        Attachments

          Activity

            People

            Assignee:
            brian.postlethwaite Brian Postlethwaite
            Reporter:
            richardleaf Richard Leaf
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Vote Date: