HL7 EHR-S FM R2.1.1 - Dental Health Functional Profile, Release 2
2.0.0-ballot - Informative United States of America flag

HL7 EHR-S FM R2.1.1 - Dental Health Functional Profile, Release 2, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/dhfp-ig/ and changes regularly. See the Directory of published versions

: POP.10 Manage Population Health Study-Related Identifiers (Function)

Page standards status: Informative Maturity Level: 1

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="DHFPR2-POP.10"/>
  <meta>
    <profile
             value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"/>
  </meta>
  <language value="en"/>
  <text>
    <status value="extensions"/>
    <div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">
    
             
    
    
    <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>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></div>
    
    
    
    <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>
    
    <table id="statements" class="grid dict">
        
        <tr>
            <td style="padding-left: 4px;">
            POP.10#01
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <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>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            POP.10#02
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHALL provide the ability to manage the site identification number(s) as assigned by the Sponsor.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            POP.10#03
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <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>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            POP.10#04
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <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>
                
            </td>
        </tr>
        
    </table>
</div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="informative"/>
  </extension>
  <extension
             url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
    <valueCode value="NC"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="ehr"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/ehrs/us/dhfpr2/ImplementationGuide/hl7.ehrs.us.dhfpr2"/>
      </extension>
    </valueInteger>
  </extension>
  <url value="http://hl7.org/ehrs/us/dhfpr2/Requirements/DHFPR2-POP.10"/>
  <version value="2.0.0-ballot"/>
  <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="2025-12-19T08:44:27+00:00"/>
  <publisher value="HL7 International / Electronic Health Records"/>
  <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="urn:iso:std:iso:3166"/>
      <code value="US"/>
    </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."/>
  <derivedFrom
               value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-POP.10"/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-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."/>
    <derivedFrom value="POP.10#1"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-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."/>
    <derivedFrom value="POP.10#2"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-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."/>
    <derivedFrom value="POP.10#3"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-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."/>
    <derivedFrom value="POP.10#4"/>
  </statement>
</Requirements>