PackagesCanonicalsLogsProblems
    Packages
    hl7.fhir.core@1.4.0
    http://hl7.org/fhir/CodeSystem/example
{
  "description": "This is an example code system that includes all the ACME codes for serum/plasma cholesterol from v2.36.",
  "_filename": "codesystem-example.json",
  "package_name": "hl7.fhir.core",
  "date": "2016-01-28",
  "meta": {
    "profile": [ "http://hl7.org/fhir/StructureDefinition/codesystem-shareable-definition" ]
  },
  "publisher": "HL7 International",
  "content": "complete",
  "name": "ACME Codes for Cholesterol in Serum/Plasma",
  "_caseSensitive": {
    "fhir_comments": [ "    it's often unstated - are codes case sensitive or not. And \n       it can be the cause of operational or clinical safety problems. \n       So FHIR requires that it always be specified.    " ]
  },
  "type": null,
  "experimental": "true",
  "resourceType": "CodeSystem",
  "title": null,
  "package_version": "1.4.0",
  "status": "draft",
  "id": "a95c5e99-1a87-48d4-ad21-aa960a4ea2c6",
  "kind": null,
  "url": "http://hl7.org/fhir/CodeSystem/example",
  "identifier": {
    "value": "internal-cholesterol-inl",
    "system": "http://acme.com/identifiers/codesystems",
    "fhir_comments": [ "    an imaginary identifier. This is a non FHIR identifier - might be used in a \n\t  v2 context (though you always need to translate namespaces for v2)    " ]
  },
  "concept": [ {
    "code": "chol-mmol",
    "display": "SChol (mmol/L)",
    "definition": "Serum Cholesterol, in mmol/L",
    "designation": [ {
      "use": {
        "code": "internal-label",
        "system": "http://acme.com/config/fhir/codesystems/internal"
      },
      "value": "From ACME POC Testing"
    } ],
    "fhir_comments": [ "    \n\t\t\tACME's defined definitions. Note that these are not \n\t\t\t*good* definitions - but they are very commonly the kind \n\t\t\tof definitions that are encountered in production\n\t\t   " ]
  }, {
    "code": "chol-mass",
    "display": "SChol (mg/L)",
    "definition": "Serum Cholesterol, in mg/L",
    "designation": [ {
      "use": {
        "code": "internal-label",
        "system": "http://acme.com/config/fhir/codesystems/internal"
      },
      "value": "From Paragon Labs"
    } ]
  }, {
    "code": "chol",
    "display": "SChol",
    "definition": "Serum Cholesterol",
    "designation": [ {
      "use": {
        "code": "internal-label",
        "system": "http://acme.com/config/fhir/codesystems/internal"
      },
      "value": "Obdurate Labs uses this with both kinds of units..."
    } ]
  } ],
  "caseSensitive": true,
  "version": "20160128",
  "_version": {
    "fhir_comments": [ "    for version, we are going to simply use the day of publication. This is also \n    arbitrary - whatever is here is what people use to refer to the version. \n    Could also be a UUID too. Note that you should change the identify of the code \n    system, not the version, if existing codes are redefined (e.g. don't do that!)   " ]
  },
  "contact": [ {
    "name": "FHIR project team",
    "telecom": [ {
      "value": "http://hl7.org/fhir",
      "system": "other"
    } ]
  } ],
  "_url": {
    "fhir_comments": [ "    \n\t  for this example, we use a real URI, since this example does have a canonical address\n\t\tat which it's posted. Alternatively, We could have used an OID, or a UUID \n\n    note that since we give a literal URL here, there's an expectation \n\t\t\tthat accessing that URL will give some form of representation of \n\t\t\tthe full code system, or a pointer about how to get more infomration. \n\t\n\t\t\tThis is not an absolute requirement, but it may be enforced by some \n\t\t\tservers - for instance, the HL7 valueset registry will.    " ]
  }
}