This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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: R5 R4B R4
Financial Management Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
Canonical Mapping for "Contract Resource Status Codes"
<?xml version="1.0" encoding="UTF-8"?> <ConceptMap xmlns="http://hl7.org/fhir"> <id value="sc-contract-status"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2> ContractResourceStatusCodesCanonicalMap (http://hl7.org/fhir/ConceptMap/sc-contract-status)</h2> <p> Mapping from <a href="valueset-contract-status.html">http://hl7.org/fhir/ValueSet/contract-status</a> to <a href="valueset-resource-status.html">http://hl7.org/fhir/ValueSet/resource-status</a> </p> <p> DRAFT. Published on 31 Dec. 2019, 9:03:40 pm by Financial Management ( <a href="http://hl7.org/fhir">http://hl7.org/fhir</a> ). </p> <div> <p> Canonical Mapping for "This value set contract specific codes for status."</p> </div> <br/> <table class="grid"> <tr> <td> <b> Source Code</b> </td> <td> <b> Relationship</b> </td> <td> <b> Destination Code</b> </td> </tr> <tr> <td> entered-in-error</td> <td> equivalent</td> <td> error</td> </tr> <tr> <td> offered</td> <td> equivalent</td> <td> proposed</td> </tr> <tr> <td> negotiable,policy</td> <td> equivalent</td> <td> draft</td> </tr> <tr> <td> executable,resolved</td> <td> equivalent</td> <td> active</td> </tr> <tr> <td> disputed</td> <td> equivalent</td> <td> suspended</td> </tr> <tr> <td> revoked</td> <td> equivalent</td> <td> failed</td> </tr> <tr> <td> amended,appended,renewed</td> <td> equivalent</td> <td> replaced</td> </tr> <tr> <td> executed</td> <td> equivalent</td> <td> complete</td> </tr> <tr> <td> cancelled,rejected,terminated</td> <td> equivalent</td> <td> abandoned</td> </tr> </table> </div> </text> <url value="http://hl7.org/fhir/ConceptMap/sc-contract-status"/> <version value="4.2.0"/> <name value="ContractResourceStatusCodesCanonicalMap"/> <title value="Canonical Mapping for "Contract Resource Status Codes""/> <status value="draft"/> <date value="2019-12-31T21:03:40+11:00"/> <publisher value="Financial Management"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> </contact> <description value="Canonical Mapping for "This value set contract specific codes for status.""/> <sourceCanonical value="http://hl7.org/fhir/ValueSet/contract-status"/> <targetCanonical value="http://hl7.org/fhir/ValueSet/resource-status"/> <group> <source value="http://hl7.org/fhir/contract-status"/> <target value="http://hl7.org/fhir/resource-status"/> <element> <code value="entered-in-error"/> <target> <code value="error"/> <relationship value="equivalent"/> </target> </element> <element> <code value="offered"/> <target> <code value="proposed"/> <relationship value="equivalent"/> </target> </element> <element> <code value="negotiable,policy"/> <target> <code value="draft"/> <relationship value="equivalent"/> </target> </element> <element> <code value="executable,resolved"/> <target> <code value="active"/> <relationship value="equivalent"/> </target> </element> <element> <code value="disputed"/> <target> <code value="suspended"/> <relationship value="equivalent"/> </target> </element> <element> <code value="revoked"/> <target> <code value="failed"/> <relationship value="equivalent"/> </target> </element> <element> <code value="amended,appended,renewed"/> <target> <code value="replaced"/> <relationship value="equivalent"/> </target> </element> <element> <code value="executed"/> <target> <code value="complete"/> <relationship value="equivalent"/> </target> </element> <element> <code value="cancelled,rejected,terminated"/> <target> <code value="abandoned"/> <relationship value="equivalent"/> </target> </element> </group> </ConceptMap>
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.