ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - CI Build

Publish Box goes here

: Trust Infrastructure - XML Representation

Active as of 2024-11-23

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2.1-TI"/>
  <meta>
    <profile value="http://hl7.org/ehrs/StructureDefinition/FMSection"/>
  </meta>
  <text>
    <status value="extensions"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
    <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 an EHR 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 &quot;TI&quot;.
Example:
Care Provision (CP) and Care Provision Support (CPS) functions must operate in a secure electronic environment. For example, Trust Infrastructure functions provide a secure environment for the CP immunization registration query function. Subsequently a CP function reports (transmits) the child's immunization event in a secure manner via another TI exchange function. TI functions also transparently provide other essential services, such as periodic backups of a child's health record and an audit trail of all accesses to that record.</p>
</div></span>

    

    
    <span id="actors"><b>Actors:</b><br/> Many TI functions are performed transparently by EHR systems – at least from the perspective of users whose role is primarily clinical. Many TI functions occur in the background without end user intervention. Other actors may interact more directly with TI functions: System Administrators (to manage and monitor system operations, configurations, backups, etc.), Security Administrators (to implement security policies for authentication, authorization, access control, audit, identity and signatures, etc.).</span>
    

    
    <table id="statements" class="grid dict">
        
    </table>
</div>
  </text>
  <extension
             url="http://hl7.org/ehrs/StructureDefinition/requirements-actors">
    <valueString
                 value="Many TI functions are performed transparently by EHR systems – at least from the perspective of users whose role is primarily clinical. Many TI functions occur in the background without end user intervention. Other actors may interact more directly with TI functions: System Administrators (to manage and monitor system operations, configurations, backups, etc.), Security Administrators (to implement security policies for authentication, authorization, access control, audit, identity and signatures, etc.)."/>
  </extension>
  <url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-TI"/>
  <version value="2.1.0"/>
  <name value="Trust_Infrastructure"/>
  <title value="Trust Infrastructure"/>
  <status value="active"/>
  <date value="2024-11-23T08:20:40+00:00"/>
  <publisher value="EHR WG"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description
               value="The Trust Infrastructure (TI) Section consists of functions common to an EHR 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 &quot;TI&quot;.
Example:
Care Provision (CP) and Care Provision Support (CPS) functions must operate in a secure electronic environment. For example, Trust Infrastructure functions provide a secure environment for the CP immunization registration query function. Subsequently a CP function reports (transmits) the child's immunization event in a secure manner via another TI exchange function. TI functions also transparently provide other essential services, such as periodic backups of a child's health record and an audit trail of all accesses to that record."/>
</Requirements>