<?xml version=“1.0” encoding=“UTF-8”?> <AllergyIntolerance xmlns=“hl7.org/fhir”>

<id value="fishallergy"/>
<meta>
  <security>
    <system value="http://terminology.hl7.org/CodeSystem/v3-ActReason"/>
    <code value="HTEST"/>
    <display value="test health data"/>
  </security>
</meta>

<!--  an identifier used for this Adverse Reaction Risk  -->
<identifier>
  <system value="http://acme.com/ids/patients/risks"/>
  <value value="49476535"/>
</identifier>

<clinicalStatus>
  <coding>
    <system value="http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical"/>
    <code value="active"/>
    <display value="Active"/>
  </coding>
</clinicalStatus>

<verificationStatus>
  <coding>
    <system value="http://terminology.hl7.org/CodeSystem/allergyintolerance-verification"/>
    <code value="confirmed"/>
    <display value="Confirmed"/>
  </coding>
</verificationStatus>

<!--  this categorization is implied by "cashew nut" and therefore basically 
  redundant, but many systems collect this field anyway, since it's either 
  useful when the substance is not coded, or it's quicker to sort/filter on
  than using terminology based reasoning  -->
<category value="food"/>

<!--  subtance - either coded, or text. A few times, 
  there's a full description of a complex substance - in these caes, use the
  extension [url] to refer to a Substance resource  -->
<code>
  <coding>
    <system value="http://snomed.info/sct"/>
    <code value="227037002"/>
    <display value="Fish - dietary (substance)"/>
  </coding>
  <text value="Allergic to fresh fish. Tolerates canned fish"/>
</code>

<!--  the patient that actually has the risk of adverse reaction  -->
<patient>
  <reference value="Patient/example"/>
</patient>

<!--  the date that this entry was recorded  -->  
<recordedDate value="2015-08-06T15:37:31-06:00"/>

<!--  who made the record / last updated it  -->
<recorder>
  <reference value="Practitioner/example"/>
</recorder>

</AllergyIntolerance>