DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 2). 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 R2

Immunization-example

This is the narrative for the resource. See also the XML or JSON format.


Generated Narrative with Details

id: example

identifier: urn:oid:1.3.6.1.4.1.21367.2005.3.7.1234

status: completed

date: 10/01/2013

vaccineCode: Fluvax (Influenza) (Details : {urn:oid:1.2.36.1.2001.1005.17 code 'FLUVAX' = '??)

patient: Patient/example

wasNotGiven: false

reported: false

performer: Practitioner/example

requester: Practitioner/example

encounter: Encounter/example

manufacturer: Organization/hl7

location: Location/1

lotNumber: AAJN11K

expirationDate: 15/02/2015

site: left arm (Details : {http://hl7.org/fhir/v3/ActSite code 'LA' = 'left arm', given as 'left arm'})

route: Injection, intramuscular (Details : {http://hl7.org/fhir/v3/RouteOfAdministration code 'IM' = 'Injection, intramuscular', given as 'Injection, intramuscular'})

doseQuantity: 5 mg (Details: http://unitsofmeasure.org code mg = '??')

note: Notes on adminstration of vaccine

Explanations

-Reason
*429060002 (Details : {SNOMED CT code '429060002' = '429060002)

Reactions

-DateDetailReported
*10/01/2013Observation/exampletrue

VaccinationProtocols

-DoseSequenceDescriptionAuthoritySeriesSeriesDosesTargetDiseaseDoseStatusDoseStatusReason
*1Vaccination Protocol Sequence 1Organization/hl7Vaccination Series 121857005 (Details : {SNOMED CT code '1857005' = '1857005)Counts (Details : {http://hl7.org/fhir/vaccination-protocol-dose-status code 'count' = 'Counts', given as 'Counts'})Cold chain break (Details : {http://hl7.org/fhir/vaccination-protocol-dose-status-reason code 'coldchbrk' = 'Cold chain break', given as 'Cold chain break'})

 

Other examples that reference this example:

  • ImmunizationRecommendation/General
  •  

    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.