Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Patient Matching. Patient matching and record linkage help address interoperability by determining whether records - both those held within a single facility and those in different healthcare organizations – correctly refer to a specific individual.  Matching methods use demographic information, such as name and date of birth. In this context, the term “patient matching” refers to the process that identifies and matches records that represent the same individual within the same enterprise, while record linkage refers to the matching that occurs when data is exchanged between enterprises. 

Patient Mediated. Patient authorizes access to their data by a third party when it is under patient's management and not the data creator (e.g. an intermediary allows patient to manage their own data).

Patient Directed. Patient authorizes access to their data to a third party through an app as in SMART app launch workflow using the patient's credentials for authenticating themselves at the data holder organization which is the data creator.


2 Use Cases and Roles

Build from items the Use Cases team originally tagged as applicable to us (a few are linked in action items from this meeting) + Core Capabilities flagged for Identity

...

TEFCA-specific (per draft 2; will need updating): Recording & communicating a Meaningful Choice; Authorizing an Individual Access Request

Patient Mediated. Patient authorizes access to their data by a third party when it is under patient's management and not the data creator (e.g. an intermediary allows patient to manage their own data).

Patient Directed. Patient authorizes access to their data to a third party through an app as in SMART app launch workflow using the patient's credentials for authenticating themselves at the data holder organization which is the data creator.

3 Compilation of industry-wide digital identity and patient matching projects

...

Risk Analysis (question) or similar discussion Identifying the Identity Level of Assurance that is appropriate for various use cases, for example a patient's access to their own data or to make a consent, covered entity access to health data for Treatment/Payment/Operations, verification of demographic attributes to flag as verified and with Patient resource or Encounter context. 

Process Include process for considering verifying a photo to be verified for use in matching, e.g., as in 800-63 where photo taken during proofing event is confirmed as matching with photo on identity evidence for IAL2 remote unsupervised etc. 

Identity verification use case leveraging the parent's identity verification in order to shore up identity of the child.

...