HL7 Personal Health Record System Functional Model, Release 2, published by EHR WG. This guide is not an authorized publication; it is the continuous build for version 2.0.1-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phrsfm-ig/ and changes regularly. See the Directory of published versions
: TI.4 Standard Terminology and Terminology Services (Header) - TTL Representation
Raw ttl | Download
@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
# - resource -------------------------------------------------------------------
a fhir:Requirements ;
fhir:nodeRole fhir:treeRoot ;
fhir:id [ fhir:v "PHRSFMR2-TI.4"] ; #
fhir:meta [
( fhir:profile [
fhir:v "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMHeader"^^xsd:anyURI ;
fhir:link <http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMHeader> ] )
] ; #
fhir:text [
fhir:status [ fhir:v "extensions" ] ;
fhir:div "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Support semantic interoperability through the use of standard terminologies, standard terminology models and standard terminology services.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The purpose of supporting terminology standards and services is to enable semantic interoperability. Interoperability is demonstrated by the consistency of human and machine interpretation of shared data and reports. It includes the capture and support of consistent data for templates and decision support logic.</p>\n<p>Terminology standards pertain to concepts, representations, synonyms, relationships and computable (machine-readable) definitions. Terminology services provide a common way for managing and retrieving these items, including historically correct version interpretation. Terminology services need to support legal requirements for retrospective health record information and system data.</p>\n</div></span>\n \n\n \n \n \n\n \n <table id=\"statements\" class=\"grid dict\">\n \n </table>\n</div>"^^rdf:XMLLiteral
] ; #
fhir:extension ( [
fhir:url [ fhir:v "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"^^xsd:anyURI ] ;
fhir:value [
a fhir:code ;
fhir:v "ehr" ]
] ) ; #
fhir:url [ fhir:v "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-TI.4"^^xsd:anyURI] ; #
fhir:version [ fhir:v "2.0.1-ballot"] ; #
fhir:name [ fhir:v "TI_4_Standard_Terminology_and_Terminology_Services"] ; #
fhir:title [ fhir:v "TI.4 Standard Terminology and Terminology Services (Header)"] ; #
fhir:status [ fhir:v "active"] ; #
fhir:date [ fhir:v "2025-08-29T14:03:44+00:00"^^xsd:dateTime] ; #
fhir:publisher [ fhir:v "EHR WG"] ; #
fhir:contact ( [
( fhir:telecom [
fhir:system [ fhir:v "url" ] ;
fhir:value [ fhir:v "http://www.hl7.org/Special/committees/ehr" ] ] )
] ) ; #
fhir:description [ fhir:v "Support semantic interoperability through the use of standard terminologies, standard terminology models and standard terminology services."] ; #
fhir:purpose [ fhir:v "The purpose of supporting terminology standards and services is to enable semantic interoperability. Interoperability is demonstrated by the consistency of human and machine interpretation of shared data and reports. It includes the capture and support of consistent data for templates and decision support logic.\r\n\r\nTerminology standards pertain to concepts, representations, synonyms, relationships and computable (machine-readable) definitions. Terminology services provide a common way for managing and retrieving these items, including historically correct version interpretation. Terminology services need to support legal requirements for retrospective health record information and system data."] . #
|
Propose a change