Publication Build: This will be filled in by the publication tooling
: Trust Infrastructure - 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"] ; #
fhir:meta [
( fhir:profile [
fhir:v "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMSection"^^xsd:anyURI ;
fhir:link <http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMSection> ] )
] ; #
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>The Trust Infrastructure (TI) Section consists of functions common to a PHR System infrastructure, particularly those functions foundational to system operations, security, efficiency and data integrity assurance, safeguards for privacy and confidentiality, and interoperability with other systems. TI functions are core and foundational to all other functions of the Model (Care Provision, Care Provision Support, Population Health, Administrative Support and Record Infrastructure). Note extensive reference to TI functions in Overarching Criteria. TI functions may be implemented within the architecture of a single system or across a tightly coupled suite of systems (applications).All functions within the Trust Infrastructure Section have an identifier starting with “TI”.</p>\n<p>The RI and TI Sections are identical between the PHR and EHR System Functional Models, reflecting the need for common and compatible record management and trust infrastructures. Note that there may be some functions more directly applicable to EHR systems than PHR systems.</p>\n</div></span>\n\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> $EX$$AC$, ehr</span>\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/ehrs/uv/phrsfmr2/StructureDefinition/requirements-actors"^^xsd:anyURI ] ;
fhir:value [
a fhir:string ;
fhir:v "$EX$$AC$" ]
] [
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"^^xsd:anyURI] ; #
fhir:version [ fhir:v "2.0.1-ballot"] ; #
fhir:name [ fhir:v "Trust_Infrastructure"] ; #
fhir:title [ fhir:v "Trust Infrastructure"] ; #
fhir:status [ fhir:v "active"] ; #
fhir:date [ fhir:v "2025-04-04T11:42:51+11: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 "The Trust Infrastructure (TI) Section consists of functions common to a PHR System infrastructure, particularly those functions foundational to system operations, security, efficiency and data integrity assurance, safeguards for privacy and confidentiality, and interoperability with other systems. TI functions are core and foundational to all other functions of the Model (Care Provision, Care Provision Support, Population Health, Administrative Support and Record Infrastructure). Note extensive reference to TI functions in Overarching Criteria. TI functions may be implemented within the architecture of a single system or across a tightly coupled suite of systems (applications).All functions within the Trust Infrastructure Section have an identifier starting with “TI”.\r\n\r\nThe RI and TI Sections are identical between the PHR and EHR System Functional Models, reflecting the need for common and compatible record management and trust infrastructures. Note that there may be some functions more directly applicable to EHR systems than PHR systems."] . #
|
Propose a change