Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
V2.x Message Specification (V2)
-
V2.9
-
Patient Administration
-
Patient Identification (PID)
-
Patient Administration (Chapter 3)
-
3.4.2.39
-
-
Craig Newman / Riki Merrick : 3-0-0
-
Enhancement
-
Compatible, substantive
Description
This issue came up in a discussion with LisaRNelson in the 2023-06-02 V2 Management Notes. Please involve her in any discussions.
For consistency with the USCDI Tribal Affiliation data element and the FHIR US Core Tribal Affiliation Extension we need a way to represent tribal affiliation in V2 Messaging. A patient may be informally affiliated with a tribe without being an enrolled legal citizen of that tribe. This is relevant to SDOH. For example, the patient might be affiliated with a tribe by living on tribal land or being married to a tribal citizen..
V2MG members discussed two potential solutions.
- Rename PID-39 from "Tribal Citizenship" to "Tribal Citizenship or Affiliation", and update the definition accordingly. This would maintain backward compatibility and be fairly easy to implement, however it wouldn't clearly distinguish between affiliation versus legal citizenship which might create issues when mapping V2 to CDA and FHIR.
- Add a new optional repeating PID-41 "Tribal Affiliation" field (suggested by RikiM). This would require more software changes for implementers, but it would explicitly differentiate between citizenship versus affiliation and would allow a cleaner mapping to CDA and FHIR.
PA members might be able to think of other options beyond those two.
Attachments
Issue Links
- relates to
-
V2-25350 Wrong table binding on PID-39 (Tribal Citizenship)
- Triaged
-
FHIR-39866 Thanks for adding the Tribal Affiliation extension!
- Resolved - No Change
-
FHIR-40203 Tribal Affiliation Extension - enrollment and alignment with eCR
- Published
- mentioned in
-
Page Loading...