HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 - Normative

HL7 Electronic Health Record System Functional Model, Release 2.1.1, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/ehrsfm-ig/ and changes regularly. See the Directory of published versions

## : RI.2 Record Synchronization (Function)

Page standards status: Normative

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 "EHRSFMR2-RI.2"] ; #
      fhir:meta [
        ( fhir:profile [
    fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"^^xsd:anyURI ;
    fhir:l <http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction>     ] )
      ] ; #
      fhir:language [ fhir:v "en"] ; #
      fhir:text [
    fhir:status [ fhir:v "extensions" ] ;
    fhir:div [ fhir:v "<div xml:lang=\"en\" xmlns=\"http://www.w3.org/1999/xhtml\" lang=\"en\">\n    \n    \n    <div id=\"description\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>An EHR-S may consist of a set of components or applications; each application manages a subset of the health information. Therefore it is important that, through various interoperability mechanisms, an EHR-S maintains all the relevant information regarding the health record in synchrony. For example, if a physician orders an MRI, a set of diagnostic images and a radiology report will be created. As a result, the patient demographic information, the order for MRI, the diagnostic images associated with the order, and the report associated with the study must all be synchronized in order for the clinicians to receive a synchronized view the complete record (with respect to time and geographic location).Date and time need to be consistent across the applications that are part of the EHR system.</p>\n<p>Synchronization demonstrates a sequence and chain of events for reconstruction and is relevant during a legal proceeding. Maintenance of synchronization activities could be relevant during a legal proceeding.</p>\n<p>Note: Standards exist for Consistent Date and Time.</p>\n</div></div>\n    \n    \n    \n    <div id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></div>\n    \n    <table id=\"statements\" class=\"grid dict\">\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.2#01\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHALL conform to function <a href=\"Requirements-EHRSFMR2-TI.5.1.html\">TI.5.1</a> (Application and Structured-Document Interchange Standards).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.2#02\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHOULD conform to function <a href=\"Requirements-EHRSFMR2-TI.3.html\">TI.3</a> (Registry and Directory Services).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.2#03\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHOULD provide the ability to link Record Entries to external information.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.2#04\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHOULD store the location of each known Record Entry in order to enable authorized access to a complete logical health record if the EHR is distributed among several applications, services, or devices within the EHR-S.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.2#05\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHALL provide the ability to manage date and time-related information between applications, components, services, systems, and devices.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n    </table>\n</div>"^^rdf:XMLLiteral ]
      ] ; #
      fhir:extension ( [
    fhir:url [
    fhir:v "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"^^xsd:anyURI ;
    fhir:l <http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status>     ] ;
    fhir:value [
    a fhir:Code ;
    fhir:v "normative"     ]
      ] [
    fhir:url [
    fhir:v "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"^^xsd:anyURI ;
    fhir:l <http://hl7.org/fhir/StructureDefinition/structuredefinition-wg>     ] ;
    fhir:value [
    a fhir:Code ;
    fhir:v "ehr"     ]
      ] ) ; #
      fhir:url [
    fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-RI.2"^^xsd:anyURI ;
    fhir:l <http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-RI.2>
      ] ; #
      fhir:version [ fhir:v "2.1.1"] ; #
      fhir:name [ fhir:v "RI_2_Record_Synchronization"] ; #
      fhir:title [ fhir:v "RI.2 Record Synchronization (Function)"] ; #
      fhir:status [ fhir:v "active"] ; #
      fhir:date [ fhir:v "2025-12-13T09:06:06+00:00"^^xsd:dateTime] ; #
      fhir:publisher [ fhir:v "HL7 International / Electronic Health Records"] ; #
      fhir:contact ( [
        ( fhir:telecom [
    fhir:system [ fhir:v "url" ] ;
    fhir:value [ fhir:v "http://www.hl7.org/Special/committees/ehr" ]     ] )
      ] ) ; #
      fhir:description [ fhir:v "Manage Record Synchronization"] ; #
      fhir:jurisdiction ( [
        ( fhir:coding [
    fhir:system [
    fhir:v "http://unstats.un.org/unsd/methods/m49/m49.htm"^^xsd:anyURI ;
    fhir:l <http://unstats.un.org/unsd/methods/m49/m49.htm>       ] ;
    fhir:code [ fhir:v "001" ] ;
    fhir:display [ fhir:v "World" ]     ] )
      ] ) ; #
      fhir:purpose [ fhir:v "An EHR-S may consist of a set of components or applications; each application manages a subset of the health information. Therefore it is important that, through various interoperability mechanisms, an EHR-S maintains all the relevant information regarding the health record in synchrony. For example, if a physician orders an MRI, a set of diagnostic images and a radiology report will be created. As a result, the patient demographic information, the order for MRI, the diagnostic images associated with the order, and the report associated with the study must all be synchronized in order for the clinicians to receive a synchronized view the complete record (with respect to time and geographic location).Date and time need to be consistent across the applications that are part of the EHR system.\n\nSynchronization demonstrates a sequence and chain of events for reconstruction and is relevant during a legal proceeding. Maintenance of synchronization activities could be relevant during a legal proceeding.\n\nNote: Standards exist for Consistent Date and Time."] ; #
      fhir:statement ( [
        ( fhir:extension [
    fhir:url [
    fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ;
    fhir:l <http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent>       ] ;
    fhir:value [
    a fhir:Boolean ;
    fhir:v false       ]     ] ) ;
    fhir:key [ fhir:v "EHRSFMR2-RI.2-01" ] ;
    fhir:label [ fhir:v "RI.2#01" ] ;
        ( fhir:conformance [ fhir:v "SHALL" ] ) ;
    fhir:conditionality [ fhir:v false ] ;
    fhir:requirement [ fhir:v "The system SHALL conform to function [TI.5.1](Requirements-EHRSFMR2-TI.5.1.html) (Application and Structured-Document Interchange Standards)." ] ;
    fhir:derivedFrom [ fhir:v "EHR-S_FM_R1.1 IN.2.3#1" ]
      ] [
        ( fhir:extension [
    fhir:url [
    fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ;
    fhir:l <http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent>       ] ;
    fhir:value [
    a fhir:Boolean ;
    fhir:v false       ]     ] ) ;
    fhir:key [ fhir:v "EHRSFMR2-RI.2-02" ] ;
    fhir:label [ fhir:v "RI.2#02" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v false ] ;
    fhir:requirement [ fhir:v "The system SHOULD conform to function [TI.3](Requirements-EHRSFMR2-TI.3.html) (Registry and Directory Services)." ] ;
    fhir:derivedFrom [ fhir:v "EHR-S_FM_R1.1 IN.2.3#2" ]
      ] [
        ( fhir:extension [
    fhir:url [
    fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ;
    fhir:l <http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent>       ] ;
    fhir:value [
    a fhir:Boolean ;
    fhir:v false       ]     ] ) ;
    fhir:key [ fhir:v "EHRSFMR2-RI.2-03" ] ;
    fhir:label [ fhir:v "RI.2#03" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v false ] ;
    fhir:requirement [ fhir:v "The system SHOULD provide the ability to link Record Entries to external information." ] ;
    fhir:derivedFrom [ fhir:v "EHR-S_FM_R1.1 IN.2.3#3" ]
      ] [
        ( fhir:extension [
    fhir:url [
    fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ;
    fhir:l <http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent>       ] ;
    fhir:value [
    a fhir:Boolean ;
    fhir:v false       ]     ] ) ;
    fhir:key [ fhir:v "EHRSFMR2-RI.2-04" ] ;
    fhir:label [ fhir:v "RI.2#04" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v false ] ;
    fhir:requirement [ fhir:v "The system SHOULD store the location of each known Record Entry in order to enable authorized access to a complete logical health record if the EHR is distributed among several applications, services, or devices within the EHR-S." ] ;
    fhir:derivedFrom [ fhir:v "EHR-S_FM_R1.1 IN.2.3#4" ]
      ] [
        ( fhir:extension [
    fhir:url [
    fhir:v "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"^^xsd:anyURI ;
    fhir:l <http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent>       ] ;
    fhir:value [
    a fhir:Boolean ;
    fhir:v false       ]     ] ) ;
    fhir:key [ fhir:v "EHRSFMR2-RI.2-05" ] ;
    fhir:label [ fhir:v "RI.2#05" ] ;
        ( fhir:conformance [ fhir:v "SHALL" ] ) ;
    fhir:conditionality [ fhir:v false ] ;
    fhir:requirement [ fhir:v "The system SHALL provide the ability to manage date and time-related information between applications, components, services, systems, and devices." ]
      ] ) . #