Release 4 5 Preview #1

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always be available at this URL). (v4.2.0: R5 Preview #1). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Medicationrequest0302

Pharmacy Work Group Maturity Level : N/A Standards Status : Informative Compartments : Encounter , Patient , Practitioner

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


Generated Narrative with Details

id : medrx0302

contained :

identifier : 12345689 (OFFICIAL)

status : active

intent : order

medication : id: med0320; Azithromycin 250mg capsule (product) (Details : {SNOMED CT code '324252006' = 'Azithromycin 250mg capsule', given as 'Azithromycin 250mg capsule (product)'})

subject : Donald Duck

encounter : encounter who leads to this prescription

supportingInformation : Coverage/SP1234

authoredOn : 15/01/2015 2015-01-15

requester : Patrick Pump

reasonCode reason : Traveller's Diarrhea (disorder) (Details : {SNOMED CT code '11840006' = 'Traveler's diarrhea', given as 'Traveller's Diarrhea (disorder)'})

note : Patient told to take with food

dosageInstruction : ,

DispenseRequests

- ValidityPeriod NumberOfRepeatsAllowed Quantity ExpectedSupplyDuration
* 15/01/2015 2015-01-15 --> 15/01/2016 2016-01-15 1 6 TAB (Details: http://terminology.hl7.org/CodeSystem/v3-orderableDrugForm code TAB = 'Tablet') 5 days (Details: UCUM code d = 'd')

Substitutions

- Allowed[x] Reason
* true formulary policy (Details : {http://terminology.hl7.org/CodeSystem/v3-ActReason code 'FP' = 'formulary policy', given as 'formulary policy'})

 

Other examples that reference this example:

  • MedicationAdministration/Oral Antibiotic
  • MedicationDispense/Mutliple dosage lines
  •  

    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.