Data used to categorize individuals for identification, records matching, and other purposes.

Data Element
Tribal Enrollment
Description

A tribe of which the patient is an enrolled member.
Submitted By: Laura Conn
Data Element Information
Use Case Description(s)
Use Case Description Health Equity Strategy
Estimate the breadth of applicability of the use case(s) for this data element TBD
Link to use case project page https://www.cdc.gov/ecr/index.html
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Improving provider experience of care
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) HL7 FHIR: US Public Health Tribal Affiliation extension
HL7 CDA: Tribal Affiliation template
HL7 Value Set: TribalEntityUS

https://www.hl7.org/implement/standards/product_brief.cfm?product_id=519 https://www.hl7.org/implement/standards/product_brief.cfm?product_id=436 http://terminology.hl7.org/ValueSet/v3-TribalEntityUS
Additional Specifications HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) based on FHIR R4 HL7 CDA® R2 Implementation Guide: Public Health Case Report - the Electronic Initial Case Report (eICR) HL7 FHIR: US Public Health Tribal Affiliation extension HL7 CDA: Tribal Affiliation template
Current Use Extensively used in production environments
Supporting Artifacts Soon to be published: HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) STU Release 2 Soon to be published: HL7 CDA® R2 Implementation Guide: Public Health Case Report - the Electronic Initial Case Report (eICR) Release 1, STU Release 3.0
https://www.hl7.org/implement/standards/product_brief.cfm?product_id=519 https://www.hl7.org/implement/standards/product_brief.cfm?product_id=436
Extent of exchange 5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) N/A
Restrictions on Use (e.g. licensing, user fees) N/A
Privacy and Security Concerns N/A
Estimate of Overall Burden These data elements are straightforward in nature and should not present a large burden to implement provided the EHR system is capturing the data.
Other Implementation Challenges N/A
ASTP Evaluation Details
Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
Criterion #1
Maturity - Current Standards		 Level 0 - Data element is not represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 0 - Data element is captured, stored, or accessed in limited settings such as a pilot or proof of concept demonstration.
Criterion #3
Maturity - Current Exchange		 Level 0 - Data element is electronically exchanged in limited environments, such as connectathons or pilots.
Criterion #4
Use Case(s) - Breadth of Applicability		 Level 1 - Use cases apply to several care settings or specialties.
Evaluation Comment Assessed as a comment. Tribal affiliation, rather than tribal enrollment, is recommended as only tribes determine and define tribal enrollment. Federal, state, and local entities do not have the ability to verify tribal enrollment, and use of tribal affiliation allows for the collection of what tribe(s) an individual patient identifies with, without impeding on tribal sovereignty in any way.

Comment

Log in or register to post comments