Publish Box goes here

• Narrative Content
• XML
• JSON
• TTL

: Record Infrastructure - TTL Representation

Active as of 2024-08-12

Raw ttl | Download

@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:Requirements ;
  fhir:nodeRole fhir:treeRoot ;
  fhir:id [ fhir:v "EHRSFMR2.1-RI"] ; # 
  fhir:meta [
    ( fhir:profile [
fhir:v "http://hl7.org/ehrs/StructureDefinition/FMSection"^^xsd:anyURI ;
fhir:link <http://hl7.org/ehrs/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 Record Infrastructure Section consists of functions common to EHR System record management, particularly those functions foundational to managing record lifecycle (origination, attestation, amendment, access/use, translation, transmittal/disclosure, receipt, de-identification, archive…) and record lifespan (persistence, indelibility, continuity, audit, encryption). RI functions are core and foundational to all other functions of the Model (CP, CPS, POP, AS). Note extensive reference to RI functions in Overarching Criteria. RI functions may be implemented within the architecture of a single system or across a tightly coupled suite of systems (applications).All functions within the Record Infrastructure Section have an identifier starting with “RI”.\nExample:\nCare Provision (CP) and Care Provision Support (CPS) functions are invoked by Actors taking Actions (i.e., caregivers documenting care provision). Most all Actions taken to support individual health or to provide healthcare are captured by the EHRS and persistently evidenced in the EHR record. For example, CP immunization administration functions create EHR record entries which must be persisted over time. These same entries form the basis for transmittal to central immunization registries.</p>\n</div></span>\n\n    \n\n    \n    <span id=\"actors\"><b>Actors:</b><br/> Many RI functions are performed transparently by EHR systems – at least from the perspective of users whose role is primarily clinical. Many RI functions occur in the background without end user intervention. Other actors may interact more directly with RI functions: System Administrators (to create archives of historical patient encounters or to purge records after their legal retention period has expired).</span>\n    \n\n    \n    <table id=\"statements\" class=\"grid dict\">\n        \n    </table>\n</div>"
  ] ; # 
  fhir:extension ( [
fhir:url [ fhir:v "http://hl7.org/ehrs/StructureDefinition/requirements-actors"^^xsd:anyURI ] ;
fhir:value [ fhir:v "Many RI functions are performed transparently by EHR systems – at least from the perspective of users whose role is primarily clinical. Many RI functions occur in the background without end user intervention. Other actors may interact more directly with RI functions: System Administrators (to create archives of historical patient encounters or to purge records after their legal retention period has expired)." ]
  ] ) ; # 
  fhir:url [ fhir:v "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-RI"^^xsd:anyURI] ; # 
  fhir:version [ fhir:v "0.16.0"] ; # 
  fhir:name [ fhir:v "Record_Infrastructure"] ; # 
  fhir:title [ fhir:v "Record Infrastructure"] ; # 
  fhir:status [ fhir:v "active"] ; # 
  fhir:date [ fhir:v "2024-08-12T10:56:01+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 "The Record Infrastructure Section consists of functions common to EHR System record management, particularly those functions foundational to managing record lifecycle (origination, attestation, amendment, access/use, translation, transmittal/disclosure, receipt, de-identification, archive…) and record lifespan (persistence, indelibility, continuity, audit, encryption). RI functions are core and foundational to all other functions of the Model (CP, CPS, POP, AS). Note extensive reference to RI functions in Overarching Criteria. RI functions may be implemented within the architecture of a single system or across a tightly coupled suite of systems (applications).All functions within the Record Infrastructure Section have an identifier starting with “RI”.\nExample:\nCare Provision (CP) and Care Provision Support (CPS) functions are invoked by Actors taking Actions (i.e., caregivers documenting care provision). Most all Actions taken to support individual health or to provide healthcare are captured by the EHRS and persistently evidenced in the EHR record. For example, CP immunization administration functions create EHR record entries which must be persisted over time. These same entries form the basis for transmittal to central immunization registries."] . #