ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1 - Local Development build (v0.14.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-06-01 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-POP.2.3"/>
<meta>
<profile value="http://hl7.org/ehrs/StructureDefinition/FMFunction"/>
</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>Support cohort and aggregate-level population data sharing within an organization, and/or with other organizations.</p>
</div></span>
<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>Population health data needs to be shared in a number of formats. The cohort and aggregate data (query results) may need to be shared within a facility or transmitted to other organizations on an ad hoc or periodic (namely, regularly scheduled) basis. For example, public health surveillance, monitoring and research often rely on analysis of data from multiple sources, including EHR systems. The data may need to be prepared in user-defined formats or formats defined by external parties. The care provider, public health expert, or organization may need to transmit individual or aggregate data in multiple formats (e.g., to an external statistical analytic application or to public health agencies to meet reporting requirements). Query results may need to be viewed, saved, and/or printed in pre-defined or ad hoc report formats, ( e.g., for quality reporting within the care organization). Some or all members of a cohort or population may need to be anonymized, depending on the rules governing the data sharing.</p>
</div></span>
<span id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></span>
<table id="statements" class="grid dict">
<tr>
<td style="padding-left: 4px;">
<span>POP.2.3#01</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to capture, maintain, and render a request for a population-based query result according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.2.3#02</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to capture, maintain, and render pre-defined report criteria (e.g, fields to be included in the resulting report or dataset), parameters, formats, and metadata that specify use, and/or reuse of the reported data according to scope of practice, organizational policy, and/or jurisdictional law (e.g., the metadata may indicate that the report is intended for initial, confirmatory or other analyses).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.2.3#03</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to enter, maintain, and render ad hoc (user-specified) report criteria (e.g., the fields to be included in the resulting report or dataset), parameters, formats, and metadata that specify use, and/or reuse of the reported data according to scope of practice, organizational policy, and/or jurisdictional law (e.g., the metadata may indicate that the report is intended for initial, confirmatory or other analyses).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.2.3#04</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to maintain and render the results of a query (e.g., person-level lists, case reports, or aggregates) as specified by the requestors' report criteria using a recognized or a locally-defined standard (e.g., via reporting formats that are specified by public health guidelines).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.2.3#05</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to capture, maintain, and render with reports the metadata that specify use, and/or reuse of the reported data according to scope of practice, organizational policy, and/or jurisdictional law (e.g., the metadata may indicate that the report is intended for preliminary, confirmatory or other analyses; or the metadata may also indicate that the data may only be used for surveillance purposes).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.2.3#06</span>
</td>
<td style="padding-left: 4px;">
<i>conditional</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>IF standardized transmission of the results of a query are required to/from a registry or directory, THEN the system SHALL conform to function [[TI.3]] (Registry and Directory Services).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.2.3#07</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to render the results of a query in the form of a dataset that can be used by other program areas using analytical software (e.g., statistical software programs) according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.2.3#08</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to render the results of a query according to applicable privacy and confidentially rules (to prevent identification of individuals by unauthorized parties) according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.2.3#09</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to transmit information related to individual case reports, including clinical information (e.g., test results) from a care provider to public health organizations (e.g., public health notifiable, and/or reportable condition programs) according to scope of practice, organizational policy, and/or jurisdictional law (e.g., a care provider notifies the local public health authority of an individual case of a sexually-transmitted disease that was identified during the analysis of a related query).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.2.3#10</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to capture, maintain, and render the request for a population-based query result using a recognized-standard, and/or locally-defined report format or metadata according to jurisdictional law.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-POP.2.3"/>
<version value="0.14.0"/>
<name value="POP_2_3_Support_for_Cohort_and_Aggregate_Data_Sharing"/>
<title
value="POP.2.3 Support for Cohort and Aggregate Data Sharing (Function)"/>
<status value="active"/>
<date value="2024-06-01T08:34:10+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Support cohort and aggregate-level population data sharing within an organization, and/or with other organizations."/>
<purpose
value="Population health data needs to be shared in a number of formats. The cohort and aggregate data (query results) may need to be shared within a facility or transmitted to other organizations on an ad hoc or periodic (namely, regularly scheduled) basis. For example, public health surveillance, monitoring and research often rely on analysis of data from multiple sources, including EHR systems. The data may need to be prepared in user-defined formats or formats defined by external parties. The care provider, public health expert, or organization may need to transmit individual or aggregate data in multiple formats (e.g., to an external statistical analytic application or to public health agencies to meet reporting requirements). Query results may need to be viewed, saved, and/or printed in pre-defined or ad hoc report formats, ( e.g., for quality reporting within the care organization). Some or all members of a cohort or population may need to be anonymized, depending on the rules governing the data sharing."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-POP.2.3-01"/>
<label value="POP.2.3#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture, maintain, and render a request for a population-based query result according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-POP.2.3-02"/>
<label value="POP.2.3#02"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture, maintain, and render pre-defined report criteria (e.g, fields to be included in the resulting report or dataset), parameters, formats, and metadata that specify use, and/or reuse of the reported data according to scope of practice, organizational policy, and/or jurisdictional law (e.g., the metadata may indicate that the report is intended for initial, confirmatory or other analyses)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-POP.2.3-03"/>
<label value="POP.2.3#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to enter, maintain, and render ad hoc (user-specified) report criteria (e.g., the fields to be included in the resulting report or dataset), parameters, formats, and metadata that specify use, and/or reuse of the reported data according to scope of practice, organizational policy, and/or jurisdictional law (e.g., the metadata may indicate that the report is intended for initial, confirmatory or other analyses)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.2.3-04"/>
<label value="POP.2.3#04"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to maintain and render the results of a query (e.g., person-level lists, case reports, or aggregates) as specified by the requestors' report criteria using a recognized or a locally-defined standard (e.g., via reporting formats that are specified by public health guidelines)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-POP.2.3-05"/>
<label value="POP.2.3#05"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture, maintain, and render with reports the metadata that specify use, and/or reuse of the reported data according to scope of practice, organizational policy, and/or jurisdictional law (e.g., the metadata may indicate that the report is intended for preliminary, confirmatory or other analyses; or the metadata may also indicate that the data may only be used for surveillance purposes)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.2.3-06"/>
<label value="POP.2.3#06"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF standardized transmission of the results of a query are required to/from a registry or directory, THEN the system SHALL conform to function [[TI.3]] (Registry and Directory Services)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-POP.2.3-07"/>
<label value="POP.2.3#07"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to render the results of a query in the form of a dataset that can be used by other program areas using analytical software (e.g., statistical software programs) according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-POP.2.3-08"/>
<label value="POP.2.3#08"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to render the results of a query according to applicable privacy and confidentially rules (to prevent identification of individuals by unauthorized parties) according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-POP.2.3-09"/>
<label value="POP.2.3#09"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to transmit information related to individual case reports, including clinical information (e.g., test results) from a care provider to public health organizations (e.g., public health notifiable, and/or reportable condition programs) according to scope of practice, organizational policy, and/or jurisdictional law (e.g., a care provider notifies the local public health authority of an individual case of a sexually-transmitted disease that was identified during the analysis of a related query)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-POP.2.3-10"/>
<label value="POP.2.3#10"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture, maintain, and render the request for a population-based query result using a recognized-standard, and/or locally-defined report format or metadata according to jurisdictional law."/>
</statement>
</Requirements>