Release 4 FHIR CI-Build

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

Observation-example-date-lastmp.xml

Example Observation/date-lastmp (XML)

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

Raw XML ( canonical form + also see XML Format Specification )

Jump past Narrative

An "ask at order" response using the datetime datetype for the result value (id = "date-lastmp") 

<?xml version="1.0" encoding="UTF-8"?>


  
  (Details : {http://terminology.hl7.org/CodeSystem/observation-category code 'survey' =
           'Survey', given as 'Survey'})(Details : {LOINC code '8665-2' = 'Last menstrual period start date', given as 'Date last
           menstrual period'})
  
    
      
      
      
    
    
  
  
    
      
      
      
    
    
  
  
    
  
  
  

<Observation xmlns="http://hl7.org/fhir">
  <id value="date-lastmp"/> 
  <status value="final"/> 
  <category> 
    <coding> 
      <system value="http://terminology.hl7.org/CodeSystem/observation-category"/> 
      <code value="survey"/> 
      <display value="Survey"/> 
    </coding> 
    <text value="AOE"/> 
  </category> 
  <code> 
    <coding> 
      <system value="http://loinc.org"/> 
      <code value="8665-2"/> 
      <display value="Last menstrual period start date"/> 
    </coding> 
    <text value="Last menstrual period start date"/> 
  </code> 
  <subject> 
    <reference value="Patient/pat2"/> 
  </subject> 
  <effectiveDateTime value="2016-01-24"/> 
  <valueDateTime value="2016-12-30"/> 


</

Observation

>

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.