Allergyintolerance-qicore-example.xml

Example of QICore AllergyIntolerance (id = "qicore")

Raw XML

<AllergyIntolerance xmlns="http://hl7.org/fhir">
  <id value="qicore"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/allergyintolerance-reasonRefuted">
    <valueCodeableConcept>
      <coding>
        <system value="http://hl7.org/fhir/v3/ActReason"/>
        <code value="MED"/>
        <display value="Medical Status Altered"/>
      </coding>
    </valueCodeableConcept>
  </extension><!--    an identifier used for this Adverse Reaction Risk    -->
  <identifier>
    <system value="http://acme.com/ids/patients/risks"/>
    <value value="49476534"/>
  </identifier><!--    the date that this entry was recorded    -->
  <recordedDate value="2014-10-09T14:58:00+11:00"/><!--    who made the record / last updated it    -->
  <recorder>
    <reference value="Practitioner/example"/>
  </recorder><!--    the patient that actually has the risk of adverse reaction    -->
  <patient>
    <reference value="Patient/example"/>
  </patient><!--    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    -->
  <substance>
    <coding>
      <system value="http://snomed.info/sct"/>
      <code value="227493005"/>
      <display value="Cashew nuts"/>
    </coding>
  </substance><!--    this individual has had several reactions, and there is no
    question that the allergy is real and serious    -->
  <status value="confirmed"/>
  <criticality value="high"/><!--    note: it's often unknown whether an allergy is mediated by an immune response, and
   not as significant as once thought    -->
  <type value="immune"/><!--    this categorisation is implied by &quot;cashew nut&quot; 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"/><!--    last happened June 2012. Typically, systems either track lastOccurence,
     or a list of events.    -->
  <lastOccurence value="2012-06"/><!--    past events. There's no claim that this is all the events, and
     that should not be assumed    -->
  <event><!--   
      It's possible to list specific things to which the patient responded,
      e.g. chocolate (that happened to contain cashew nuts). This event has
      such a specific substance. Note that systems should ensure that what
      goes in here does not conflict with the substance above, and systems
      processing the data can be sure that what is here does not contravene
      the substance above
       -->
    <substance>
      <coding>
        <system value="http://www.nlm.nih.gov/research/umls/rxnorm"/>
        <code value="C3214954"/>
        <display value="cashew nut allergenic extract Injectable Product"/>
      </coding>
    </substance><!--    this was a challenge protocol    -->
    <certainty value="confirmed"/>
    <manifestation>
      <coding>
        <system value="http://snomed.info/sct"/>
        <code value="39579001"/>
        <display value="Anaphylactic reaction"/>
      </coding>
    </manifestation>
    <description value="Challenge Protocol. Severe Reaction to 1/8 cashew. Epinephrine administered"/>
    <onset value="2012-06-12"/>
    <severity value="severe"/>
  </event>
  <event><!--    this was the first occurence    -->
    <certainty value="likely"/>
    <manifestation>
      <coding>
        <system value="http://snomed.info/sct"/>
        <code value="64305001"/>
        <display value="Urticaria"/>
      </coding>
    </manifestation>
    <onset value="2004"/>
    <severity value="moderate"/>
  </event>
</AllergyIntolerance>