Release 4B 5

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0: R5 - STU ). The This is the current published version which supercedes in it's permanent home (it will always be available at this version is 5.0.0 . URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R5 R4B R4

Examplescenario-example

Example ExampleScenario/example (Narrative)

FHIR Infrastructure Work Group Maturity Level : N/A Standards Status : Informative Compartments : Not linked to any No defined compartments

This is the narrative for the resource. See also the XML , JSON or Turtle format. This example conforms to the profile ExampleScenario .

Generated Narrative ExampleScenario - Medication administration (IHE MMA)

Resource ExampleScenario "example"

status : : draft

purpose : : Purpose: this serves to enable remote performing of medication administration, by using remote / mobile devices to a) Get the planned medication administrations and b) Record the performing of these administrations without a permanent connection to the EHR.

actor actorId : Nurse type : person name : Nurse description : The Nurse actor actorId : MAP type : entity name : Nurse's Tablet description : The entity that receives the Administration Requests to show the nurse to perform them actor actorId : OP type : entity name : MAR / Scheduler description : The Medication Administration Order Placer actor actorId : MAC type : entity name : MAR / EHR description : The entity that receives the Medication Administration reports instance resourceId : iherx001 resourceType : MedicationRequest name : Initial Prescription description : The initial prescription which describes "medication X, 3 times per day" - the exact scheduling is not in the initial prescription (it is left for the care teams to decide on the schedule). instance resourceId : iherx001.001 resourceType : MedicationRequest name : Request for day 1, morning description : The administration request for day 1, morning instance resourceId : iherx001.002 resourceType : MedicationRequest name : Request for day 1, lunch description : The administration request for day 1, lunch instance resourceId : iherx001.003 resourceType : MedicationRequest name : Request for day 1, evening description : The administration request for day 1, evening instance resourceId : iherx001.004 resourceType : MedicationRequest name : Request for day 2, morning description : The administration request for day 2, morning instance resourceId : iherx001.005 resourceType : MedicationRequest name : Request for day 2, lunch description : The administration request for day 2, lunch instance resourceId : iherx001.006 resourceType : MedicationRequest name : Request for day 2, evening description : The administration request for day 2, evening instance resourceId : iheadm001a resourceType : MedicationAdministration name : Morning meds - taken description : Administration report for day 1, morning: Taken instance resourceId : iheadm001b resourceType : MedicationAdministration name : Morning meds - not taken description : Administration report for day 1, morning: NOT Taken instance resourceId : iherx001bundle resourceType : MedicationRequest name : Bundle of Medication Requests description : All the medication Requests for Day 1 containedInstance resourceId : iherx001.001 containedInstance resourceId : iherx001.002 containedInstance resourceId : iherx001.003 containedInstance resourceId : iherx001.004 containedInstance resourceId : iherx001.005 containedInstance resourceId : iherx001.006 instance resourceId : iheadm002 resourceType : MedicationAdministration name : Lunch meds - taken description : Administration report for day 1, lunch: Taken version versionId : iheadm002v1 description : Medication just taken version versionId : iheadm002v2 description : Medication rejected instance resourceId : iherxqry resourceType : SearchParameter name : Search query1 description : The search administration request for day 1, morning process title : Mobile Medication Administration description : This scenario demonstrates the process of getting the relevant medication instructions for a patient visit and reporting the results of administration. The scenario is as follows: After the prescription is issued, the institution schedules each individual administration event in the Medication Administration Record (MAR). When preparing for a visit, the nurse queries the MAR for the scheduled administrations, obtaining a bundle of records. The nurse then performs the care activities and registers the results in the device. Upon synchronization of the device and the institution, the results of administration are uploaded to the EHR, thus updating the MAR. preConditions : Medication administration requests are in the EHR / MAR, scheduled for each individual intake. postConditions : Medication administration Reports are submitted, EHR is updated. step Operations - Number Name Initiator Receiver * 1 1. Get today's schedule Nurse MAP step process title : P1. Query Administration Requests description : Query for medication administration orders,\n- For today's shifts\n- For today's patients step pause : true step Operations - Number Name Initiator Receiver * 4 Notify (alert) MAP Nurse step Operations - Number Name Initiator Receiver * 5 Read orders Nurse MAP step pause : true step Operations - Number Name Initiator Receiver * 5 Ask if patient took meds Nurse Nurse step alternative title : Patient took drugs description : Invoke if patient took medications step alternative title : No drugs description : No, patient did not take drugs step alternative title : Not clear description : Unknown whether patient took medications or not Steps - Pause * true step pause : true step Operations - Number Name Initiator Receiver * 6 Administer drug Nurse Nurse step Operations - Number Name Initiator Receiver InitiatorActive * 7 Register administration Nurse MAP true step pause : true step process title : P2. Update administration reports step pause : true step process title : P3. Upload administration reports description : The nurse's system uploads the administration results to the server ExampleScenario diagram - IHE MMA example

 

 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.