Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
Interoperable Digital Identity and Patient Matching (FHIR)
-
1.0.0-ballot
-
Patient Administration
-
Home
-
FHIR-37168 Build out "Use cases and roles". Not sure what artifact is required.
Description
Section 1.3
The IG is inconsistently applying the list of workflows defined in 1.3 to the subsequent chapters "Identity Assurance", "Patient Matching" and "Digital Identity". A canonical formulation of protocol exchange (FHIR) should be described for each of the flow in which the conveyed PII and/or digital identifiers is defined. The different flows also will help to differentiate the authentication of flows from the authentication of the data and the authorization/consent provided for the responder. Note: this is different for B2C and B2B.
Consider separating the topic of Identity Management to a different artifact that can have different timelines for adding specificity. This would allow to align with various ongoing initiatives like TEFCA and the CARIN/HHS Patient-centric Digital Identity Federation POC.
- Clarify no match when authenticating patient (sub-topic: is B2B mediated considered “authenticating patient”?)
Attachments
Issue Links
- duplicates
-
FHIR-37168 Build out "Use cases and roles". Not sure what artifact is required.
- Published
- relates to
-
FHIR-37054 Inconsistent workflows, Proper use of IAL levels
- Duplicate
-
FHIR-37168 Build out "Use cases and roles". Not sure what artifact is required.
- Published
- mentioned in
-
Page Loading...