Release 4 Snapshot 3: Connectathon 32 Base

This page is part of the Snapshot #3 for FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0 R5 , released to support Connectathon 32 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Using Codes Code Systems Value Sets Concept Maps Identifier Systems 4.4.1.372 Value Set http://hl7.org/fhir/ValueSet/http-operations

Example TerminologyCapabilities/example (Turtle)

Committee:
FHIR Infrastructure Vocabulary Work Group   Maturity Level : 2 N/A Trial Use Use Context Standards Status : Any This is a value set defined by the FHIR project. Summary Defining URL: http://hl7.org/fhir/ValueSet/http-operations Version: 4.0.1 Name: TestScriptRequestMethodCode Title: TestScriptRequestMethodCode Definition: Informative The allowable request method or HTTP operation codes. Compartments : Not linked to any defined compartments
    FHIR Infrastructure
  • Narrative Work Group OID: 2.16.840.1.113883.4.642.3.716 (for OID based terminology systems) Source Resource
  • XML / JSON This value set is used in the following places: CodeSystem: This value set is the designated 'entire code system' value set for TestScriptRequestMethodCode
    • Resource: TestScript.setup.action.operation.method (code / Required ) Resource: TestScript.setup.action.assert.requestMethod (code / Required ) 4.4.1.372.1 Content Logical Definition
  • JSON This value set includes codes from the following code systems: Include all codes defined in
    • http://hl7.org/fhir/http-operations
  • TTL

  Raw Turtle 4.4.1.372.2 Expansion (+ also see Turtle/RDF Format Specification This expansion generated 01 Nov 2019 This value set contains 7 concepts Expansion based on http://hl7.org/fhir/http-operations version 4.0.1 )

All codes from system http://hl7.org/fhir/http-operations General Terminology Capability Example

Code Display Definition delete DELETE HTTP DELETE operation. get GET HTTP GET operation. options OPTIONS HTTP OPTIONS operation. patch PATCH HTTP PATCH operation. post POST HTTP POST operation. put PUT HTTP PUT operation. head HEAD HTTP HEAD operation. 
@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

# - resource -------------------------------------------------------------------

[a fhir:TerminologyCapabilities;
  fhir:nodeRole fhir:treeRoot;
  fhir:Resource.id [ fhir:value "example"]; # 
  fhir:DomainResource.text [
     fhir:Narrative.status [ fhir:value "generated" ];
     fhir:Narrative.div "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n			<p>The EHR Server supports the following transactions for the resource Person: read, vread, \n        update, history, search(name,gender), create and updates.</p>\n			<p>The EHR System supports the following message: admin-notify::Person.</p>\n			<p>The EHR Application has a \n        <a href=\"http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796\">general document profile</a>.\n      </p>\n		</div>"
  ]; # 
  fhir:TerminologyCapabilities.url [ fhir:value "urn:uuid:68d043b5-9ecf-4559-a57a-396e0d452311"]; #     the identifier for this capability statement. 
    The identifier and version establish identifiers that other specifications etc.may use to 
    refer to the capability statement that this resource represents in a logical manner 
    rather than in a literal (URL) fashion 

    The identifier should be globally unique - a UUID, an OID, or a URL/URI
     
  fhir:TerminologyCapabilities.identifier [
     fhir:index 0;
     fhir:Identifier.system [ fhir:value "urn:ietf:rfc:3986" ];
     fhir:Identifier.value [ fhir:value "urn:oid:2.16.840.1.113883.4.642.6.2" ]
  ]; # 
  fhir:TerminologyCapabilities.version [ fhir:value "20130510"]; # 
  fhir:TerminologyCapabilities.name [ fhir:value "ACME-EHR"]; # 
  fhir:TerminologyCapabilities.title [ fhir:value "ACME EHR capability statement"]; # 
  fhir:TerminologyCapabilities.status [ fhir:value "draft"]; # 
  fhir:TerminologyCapabilities.experimental [ fhir:value "true"^^xsd:boolean]; # 
  fhir:TerminologyCapabilities.date [ fhir:value "2012-01-04"^^xsd:date]; # 
  fhir:TerminologyCapabilities.publisher [ fhir:value "ACME Corporation"]; # 
  fhir:TerminologyCapabilities.contact [
     fhir:index 0;
     fhir:ContactDetail.name [ fhir:value "System Administrator" ];
     fhir:ContactDetail.telecom [
       fhir:index 0;
       fhir:ContactPoint.system [ fhir:value "email" ];
       fhir:ContactPoint.value [ fhir:value "wile@acme.org" ]
     ]
  ]; # 
  fhir:TerminologyCapabilities.description [ fhir:value "This is the FHIR capability statement for the main EHR at ACME for the private interface - it does not describe the public interface"]; # 
  fhir:TerminologyCapabilities.kind [ fhir:value "instance"]; # 
  fhir:TerminologyCapabilities.software [
     fhir:TerminologyCapabilities.software.name [ fhir:value "TxServer" ];
     fhir:TerminologyCapabilities.software.version [ fhir:value "0.1.2" ]
  ]; # 
  fhir:TerminologyCapabilities.implementation [
     fhir:TerminologyCapabilities.implementation.description [ fhir:value "Acme Terminology Server" ];
     fhir:TerminologyCapabilities.implementation.url [ fhir:value "http://example.org/tx" ]
  ]; # 
  fhir:TerminologyCapabilities.codeSearch [ fhir:value "in-compose-or-expansion"]] . # 

# - ontology header ------------------------------------------------------------

[a owl:Ontology;
  owl:imports fhir:fhir.ttl] .

# -------------------------------------------------------------------------------------

  See the full registry of value sets defined as part of FHIR. Explanation of the columns that may appear on this page: Lvl A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used Usage note: every effort has been made to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information Source The source of the definition of the code (when the value set draws in codes defined elsewhere) Code The code (used as the code in the resource instance). If the code is in italics, this indicates ensure that the code is examples are correct and useful, but they are not selectable ('Abstract') Display The display (used in the display element of a Coding ). If there is no display, implementers should not simply display the code, but map the concept into their application Definition An explanation of the meaning normative part of the concept Comments Additional notes about how to use the code specification.