Release 5 Draft Ballot

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions


Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

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

Definition for Value SetDocumentReference Format Code Set

  "resourceType" : "ValueSet",
  "id" : "formatcodes",
  "meta" : {
    "lastUpdated" : "2022-07-01T20:18:23.459+00:00",
    "profile" : [""]
  "text" : {
    "status" : "generated",
    "div" : "<div>!-- Snipped for Brevity --></div>"
  "extension" : [{
    "url" : "",
    "valueCode" : "oo"
  "url" : "",
  "identifier" : [{
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:"
  "version" : "4.6.0",
  "name" : "DocumentReferenceFormatCodeSet",
  "title" : "DocumentReference Format Code Set",
  "status" : "active",
  "experimental" : false,
  "publisher" : "IHE",
  "description" : "The value set is defined to be the set of format codes defined by the IHE Technical Framework, and also including additional format codes defined by the    HL7. The value set is listed in HITSP C80 Table 2-153 Format Code Value Set Definition,    with additions published later by IHE as published    at   and with additions published later by HL7 as published at   This is the code specifying the technical format of the document. Along with the typeCode,    it should provide sufficient information to allow any potential document consumer to know    if it will be able to process the document. The code shall be sufficiently specific to    ensure processing/display by identifying a document encoding, structure and template. The actual list of codes here is incomplete",
  "copyright" : "Some content from IHE® Copyright © 2015 IHE International, Inc.    This content is from the IHE Technical Frameworks and Supplements,    available for free download and use at",
  "compose" : {
    "include" : [{
      "system" : ""

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.