DSTU2 STU 3 Ballot
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is

This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . For a full list of available versions, see the Directory of published versions . Page versions: . Page versions: R5 R4B R4 R3 R2

Device-example-f001-feedingtube This is the narrative for the resource. See also the

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


Generated Narrative with Details Generated Narrative with Details

id : f001 : f001

identifier : 12345 : 12345

type : Feeding tube, device (Details : {SNOMED CT code '25062003' = '25062003', given as 'Feeding tube, device'}) udiCarrier : (01)00000123000017(10)ABC123(17)120415

status : available : available

manufactureDate : 08/08/2015 type : Feeding tube, device (Details : {SNOMED CT code '25062003' = 'Feeding tube, device (physical object)', given as 'Feeding tube, device'})

expiry : 08/08/2020 manufactureDate : 08/08/2015

udi : (01)00000123000017(10)ABC123(17)120415 expirationDate : 08/08/2020

owner : : Organization/2.16.840.1.113883.19.5

location : Central Supply : Central Supply

  Other examples that reference this example:

 

Other examples that reference this example:

  • Communication/QICore Communication Communication/Alert Message
  • Communication/Alert Message MedicationAdministration/Lorazepam   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. © HL7.org 2011+. FHIR DSTU2 (v1.0.2-7202) generated on Sat, Oct 24, 2015 07:43+1100. Links: Search | Version History | Table of Contents | Compare to DSTU1
  • MedicationAdministration/TPN solution |
  •  

    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.