HL7 Terminology
2.1.15 - Continuous Process Integration (ci build)

HL7 Terminology, published by HL7 International - Vocabulary Work Group. This is not an authorized publication; it is the continuous build for version 2.1.15). This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

: ActClassConsent - XML Representation

Raw xml | Download

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-ActClassConsent"/>
  <language value="en"/>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><ul><li>Include codes from <a href="CodeSystem-v3-ActClass.html"><code>http://terminology.hl7.org/CodeSystem/v3-ActClass</code></a> where concept  is-a  <a href="CodeSystem-v3-ActClass.html#v3-ActClass-CONS">CONS</a></li></ul></div>
  <url value="http://terminology.hl7.org/ValueSet/v3-ActClassConsent"/>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.1.11.20206"/>
  <version value="2.0.0"/>
  <name value="ActClassConsent"/>
  <title value="ActClassConsent"/>
  <status value="active"/>
  <date value="2014-03-26"/>
               value="The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc.

The details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act.

The &quot;signatures&quot; to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of &quot;performer&quot;, the healthcare provider informing the patient, and &quot;consenter&quot;, the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public.

Some consent has a minimum required delay between the consent and the service, so as to allow the patient to rethink his decisions. This minimum delay can be expressed in the act definition by the ActRelationship.pauseQuantity attribute that delays the service until the pause time has elapsed after the consent has been completed."/>
  <immutable value="true"/>
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActClass"/>
        <property value="concept"/>
        <op value="is-a"/>
        <value value="CONS"/>