This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3 R2
Specifies the state change of a target Act using DocuymentCompletion codes, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".
<ValueSet xmlns="http://hl7.org/fhir"> <id value="v3-ProvenanceEventCurrentState-DC"/> <meta> <lastUpdated value="2015-12-11T17:38:40.294+11:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2>ProvenanceEventCurrentState-DC</h2> <p> Specifies the state change of a target Act using DocuymentCompletion codes, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".</p> <p>This value set includes codes from the following code systems:</p> <ul> <li>Include these codes as defined in <a href="../../v3/DocumentCompletion/index.html">http://hl7.org/fhir/v3/DocumentCompletion</a> <table> <tr> <td> <b>Code</b> </td> <td> <b>Display</b> </td> </tr> <tr> <td>AU</td> <td>authenticated</td> <td>A completion status in which a document has been signed manually or electronically by one or more individuals who attest to its accuracy. No explicit determination is made that the assigned individual has performed the authentication. While the standard allows multiple instances of authentication, it would be typical to have a single instance of authentication, usually by the assigned individual.</td> </tr> <tr> <td>DI</td> <td>dictated</td> <td>A completion status in which information has been orally recorded but not yet transcribed.</td> </tr> <tr> <td>DO</td> <td>documented</td> <td>A completion status in which document content, other than dictation, has been received but has not been translated into the final electronic format. Examples include paper documents, whether hand-written or typewritten, and intermediate electronic forms, such as voice to text.</td> </tr> <tr> <td>LA</td> <td>legally authenticated</td> <td>A completion status in which a document has been signed manually or electronically by the individual who is legally responsible for that document. This is the most mature state in the workflow progression.</td> </tr> <tr> <td>UC</td> <td>unsigned completed document</td> <td>A completion status where the document is complete and there is no expectation that the document will be signed.</td> </tr> </table> </li> </ul> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid"> <valueUri value="urn:oid:2.16.840.1.113883.1.11.20546"/> </extension> <url value="http://hl7.org/fhir/ValueSet/v3-ProvenanceEventCurrentState-DC"/> <version value="2014-08-07"/> <name value="ProvenanceEventCurrentState-DC"/> <status value="active"/> <experimental value="false"/> <publisher value="HL7 v3"/> <contact> <telecom> <system value="other"/> <value value="http://www.hl7.org"/> </telecom> </contact> <description value=" Specifies the state change of a target Act using DocuymentCompletion codes, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted"."/> <compose> <include> <system value="http://hl7.org/fhir/v3/DocumentCompletion"/> <concept> <code value="AU"/> </concept> <concept> <code value="DI"/> </concept> <concept> <code value="DO"/> </concept> <concept> <code value="LA"/> </concept> <concept> <code value="UC"/> </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.