ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - local
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - local
Publish Box goes here
| Active as of 2024-11-26 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-POP.10"/>
<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>Manage information that identifies key elements of a research or population study.</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>Research or population studies can be distinguished from each other through the proper use of identifiers for key elements. Study key elements may include identifying the study, location where the study is being performed, patient subject of study, and investigator. Identifiers are managed through their lifecycle including capture, maintenance and rendering.</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.10#01</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to manage unique research identifiers (i.e. sponsor-provided Protocol mnemonic) such that the research study can be identified.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.10#02</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 manage the site identification number(s) as assigned by the Sponsor.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.10#03</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 manage unique research subject identifiers (e.g., these identifiers could be used as a screening number prior to the subject qualifying for the clinical trial). Note: A given patient may have multiple research subject identifiers if the patient has been on multiple research studies.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.10#04</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to manage clinical research identifiers (e.g., investigator identifier or visit name) as discrete data elements.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-POP.10"/>
<version value="2.1.0"/>
<name value="POP_10_Manage_Population_Health_Study_Related_Identifiers"/>
<title
value="POP.10 Manage Population Health Study-Related Identifiers (Function)"/>
<status value="active"/>
<date value="2024-11-26T16:30:50+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Manage information that identifies key elements of a research or population study."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<purpose
value="Research or population studies can be distinguished from each other through the proper use of identifiers for key elements. Study key elements may include identifying the study, location where the study is being performed, patient subject of study, and investigator. Identifiers are managed through their lifecycle including capture, maintenance and rendering."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.10-01"/>
<label value="POP.10#01"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage unique research identifiers (i.e. sponsor-provided Protocol mnemonic) such that the research study can be identified."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.10-02"/>
<label value="POP.10#02"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to manage the site identification number(s) as assigned by the Sponsor."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.10-03"/>
<label value="POP.10#03"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to manage unique research subject identifiers (e.g., these identifiers could be used as a screening number prior to the subject qualifying for the clinical trial). Note: A given patient may have multiple research subject identifiers if the patient has been on multiple research studies."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.10-04"/>
<label value="POP.10#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage clinical research identifiers (e.g., investigator identifier or visit name) as discrete data elements."/>
</statement>
</Requirements>