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

Servicerequest-example-myringotomy

Orders and Observations Work Group Maturity Level : N/A Standards Status : Informative Compartments : Device , Encounter , Patient , Practitioner , RelatedPerson

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

Generated Narrative with Details

id : myringotomy

identifier : ret4421

basedOn : ServiceRequest for Myringotomy and insertion of tympanic ventilation tube

replaces : prior ServiceRequest

requisition : 1234

status : active

intent : order

category : Patient referral to specialist (Details : {SNOMED CT code '103696004' = 'Patient referral to specialist', given as 'Patient referral to specialist'})

priority : routine

code : Insertion of grommets (Details : {SNOMED CT code '172676009' = 'Myringotomy and insertion of short-term grommet', given as 'Myringotomy and insertion of tympanic ventilation tube'})

subject : Beverly Weaver

encounter : Beverly Waver's encounter on 2014-02-14

occurrence : ?? --> 14/03/2014 2014-03-14

authoredOn : 14/02/2014 2014-02-14

requester : Serena Shrink

performerType : ENT (Details : {http://orionhealth.com/fhir/apps/specialties code 'ent' = 'ent', given as 'ENT'})

performer : Dr Dave

reasonCode reason : For consideration of Grommets (Details )

note : In the past 2 years Beverly has had 6 instances of rt-sided Otitis media. She is falling behind her peers at school, and displaying some learning difficulties.

 

Other examples that reference this example:

  • Appointment/Example
  • Encounter/March 11th 2013

    •  

    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.