Release 5 Draft Ballot

This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Valueset-adverse-event-participant-function.xml

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

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

Definition for Value SetAdverseEvent Participant Function

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

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="adverse-event-participant-function"/> 
  <meta> 
    <lastUpdated value="2021-04-15T12:25:09.461+10:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> 
  </meta> 
  <text> 
    <status value="extensions"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <ul> 
        <li> Include these codes as defined in 
          <a href="http://terminology.hl7.org/2.1.0/CodeSystem-v3-ParticipationType.html">
            <code> http://terminology.hl7.org/CodeSystem/v3-ParticipationType</code> 
          </a> 
          <table class="none">
            <tr> 
              <td style="white-space:nowrap">
                <b> Code</b> 
              </td> 
              <td> 
                <b> Display</b> 
              </td> 
              <td> 
                <b> Definition</b> 
              </td> 
            </tr> 
            <tr> 
              <td> 
                <a href="http://terminology.hl7.org/2.1.0/CodeSystem-v3-ParticipationType.html#v3-ParticipationType-INF">INF</a> 
              </td> 
              <td> informant</td> 
              <td> A source of reported information (e.g., a next of kin who answers questions about the
                 patient's history). For history questions, the patient is logically an informant, yet
                 the informant of history questions is implicitly the subject.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="http://terminology.hl7.org/2.1.0/CodeSystem-v3-ParticipationType.html#v3-ParticipationType-PART">PART</a> 
              </td> 
              <td> Participation</td> 
              <td> Indicates that the target of the participation is involved in some manner in the act,
                 but does not qualify how.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="http://terminology.hl7.org/2.1.0/CodeSystem-v3-ParticipationType.html#v3-ParticipationType-WIT">WIT</a> 
              </td> 
              <td> witness</td> 
              <td> Only with service events. A person witnessing the action happening without doing anything.
                 A witness is not necessarily aware, much less approves of anything stated in the service
                 event. Example for a witness is students watching an operation or an advanced directive
                 witness.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="http://terminology.hl7.org/2.1.0/CodeSystem-v3-ParticipationType.html#v3-ParticipationType-AUT">AUT</a> 
              </td> 
              <td> author (originator)</td> 
              <td> **Definition:** A party that originates the Act and therefore has responsibility for the
                 information given in the Act and ownership of this Act.
                <br/>  
                <br/>  **Example:** the report writer, the person writing the act definition, the guideline author,
                 the placer of an order, the EKG cart (device) creating a report etc. Every Act should
                 have an author. Authorship is regardless of mood always actual authorship.
                <br/>  
                <br/>  Examples of such policies might include:
                <br/>  
                <br/>   *  The author and anyone they explicitly delegate may update the report;
                <br/>   *  All administrators within the same clinic may cancel and reschedule appointments created
                 by other administrators within that clinic;
                <br/>  
                <br/>  A party that is neither an author nor a party who is extended authorship maintenance rights
                 by policy, may only amend, reverse, override, replace, or follow up in other ways on this
                 Act, whereby the Act remains intact and is linked to another Act authored by that other
                 party.
              </td> 
            </tr> 
          </table> 
        </li> 
      </ul> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pc"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="draft"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1"/> 
  </extension> 
  <url value="http://hl7.org/fhir/ValueSet/adverse-event-participant-function"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.3.1443"/> 
  </identifier> 
  <version value="4.6.0"/> 
  <name value="AdverseEvent Participant Function"/> 
  <title value="AdverseEvent Participant Function"/> 
  <status value="draft"/> 
  <publisher value="FHIR Project team"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
  </contact> 
  <description value="This value set includes codes that describe the type of involvement of the actor in the
   adverse event."/> 
  <compose> 
    <include> 
      <system value="http://terminology.hl7.org/CodeSystem/v3-ParticipationType"/> 
      <concept> 
        <code value="INF"/> 
      </concept> 
      <concept> 
        <code value="PART"/> 
      </concept> 
      <concept> 
        <code value="WIT"/> 
      </concept> 
      <concept> 
        <code value="AUT"/> 
      </concept> 
    </include> 
  </compose> 
</ValueSet> 

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.