Release 5

This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4

Example ConceptMap/sc-invoice-status (JSON)

Financial Management Work GroupMaturity Level: N/AStandards Status: Informative

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

Canonical Mapping for "Invoice Status"

{
  "resourceType" : "ConceptMap",
  "id" : "sc-invoice-status",
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>InvoiceStatusCanonicalMap (http://hl7.org/fhir/ConceptMap/sc-invoice-status)</h2><p>Mapping from <a href=\"valueset-invoice-status.html\">Invoice Status</a> to <a href=\"valueset-resource-status.html\">Canonical Status Codes for FHIR Resources</a></p><p>DRAFT. Published on 2020-12-28T16:55:11+11:00 by HL7 (FHIR Project) (<a href=\"http://hl7.org/fhir\">http://hl7.org/fhir</a>, <a href=\"mailto:fhir@lists.hl7.org\">fhir@lists.hl7.org</a>). </p><div><p>Canonical Mapping for &quot;Codes identifying the lifecycle stage of an Invoice.&quot;</p>\n</div><br/><p><b>Group 1</b>Mapping from <a href=\"codesystem-invoice-status.html\">Invoice Status</a> to <a href=\"codesystem-resource-status.html\">Canonical Status Codes for FHIR Resources</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td></tr><tr><td>entered-in-error</td><td><a href=\"codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>error</td></tr><tr><td>draft</td><td><a href=\"codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>draft</td></tr><tr><td>issued</td><td><a href=\"codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>active</td></tr><tr><td>cancelled</td><td><a href=\"codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>failed</td></tr><tr><td>balanced</td><td><a href=\"codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>complete</td></tr></table></div>"
  },
  "url" : "http://hl7.org/fhir/ConceptMap/sc-invoice-status",
  "version" : "5.0.0",
  "name" : "InvoiceStatusCanonicalMap",
  "title" : "Canonical Mapping for \"Invoice Status\"",
  "status" : "draft",
  "experimental" : false,
  "date" : "2020-12-28T16:55:11+11:00",
  "publisher" : "HL7 (FHIR Project)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    },
    {
      "system" : "email",
      "value" : "fhir@lists.hl7.org"
    }]
  }],
  "description" : "Canonical Mapping for \"Codes identifying the lifecycle stage of an Invoice.\"",
  "jurisdiction" : [{
    "coding" : [{
      "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
      "code" : "001",
      "display" : "World"
    }]
  }],
  "sourceScopeCanonical" : "http://hl7.org/fhir/ValueSet/invoice-status",
  "targetScopeCanonical" : "http://hl7.org/fhir/ValueSet/resource-status",
  "group" : [{
    "source" : "http://hl7.org/fhir/invoice-status",
    "target" : "http://hl7.org/fhir/resource-status",
    "element" : [{
      "code" : "entered-in-error",
      "target" : [{
        "code" : "error",
        "relationship" : "equivalent"
      }]
    },
    {
      "code" : "draft",
      "target" : [{
        "code" : "draft",
        "relationship" : "equivalent"
      }]
    },
    {
      "code" : "issued",
      "target" : [{
        "code" : "active",
        "relationship" : "equivalent"
      }]
    },
    {
      "code" : "cancelled",
      "target" : [{
        "code" : "failed",
        "relationship" : "equivalent"
      }]
    },
    {
      "code" : "balanced",
      "target" : [{
        "code" : "complete",
        "relationship" : "equivalent"
      }]
    }]
  }]
}

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.