Release 5 R6 Ballot (1st Full Ballot)

This page is part of the FHIR Specification (v5.0.0: R5 - STU v6.0.0-ballot4: Release 6 Ballot (1st Full Ballot) (see Ballot Notes ). This is the The current published version in it's permanent home (it will always be available at this URL). is 5.0.0 . For a full list of available versions, see the Directory of published versions for published versions

Example TerminologyCapabilities/example-terminology-server (Narrative)

Maturity Level : N/A
Responsible Owner: Terminology Infrastructure Work Group Standards Status : Informative Compartments : No defined compartments

This is the narrative for the resource. See also the XML , JSON or Turtle format. This example conforms to the profile TerminologyCapabilities .

Generated Narrative: TerminologyCapabilities example-terminology-server

Resource TerminologyCapabilities "example-terminology-server" StructureDefinition Work Group : vocab

url : http://hl7.org/fhir/TerminologyCapabilities/terminology-server TerminologyCapabilities ACME Terminology Service — Terminology Capabilities

identifier : id: urn:oid:2.16.840.1.113883.4.642.6.1 Uniform Resource Identifier (URI) /urn:oid:2.16.840.1.113883.4.642.6.1

name : ACMETerminologyServiceTerminologyCapabilities

title : ACME Terminology Service — Terminology Capabilities

status : draft Draft

date : 2022-09-01

publisher : HL7 International / Terminology Infrastructure

contact : http://www.hl7.org/Special/committees/Vocab

description :

ACME Terminology Service — Terminology Capabilities

kind : instance Instance

Implementations

- Description
*

The ACME FHIR Terminology Server

codeSystem

uri : SNOMED CT International Edition http://snomed.info/sct

Versions

- Code
* http://snomed.info/sct/32506021000036107/version/20220831

content : complete Complete

codeSystem

uri : Logical Observation Identifiers, Names and Codes (LOINC) http://loinc.org

Versions

- Code
* 2.73

content : complete Complete

 

 

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.