Public Health Centers: Difference between revisions

From IDESG Wiki
Jump to navigation Jump to search
Line 18: Line 18:
# A care practice that includes outreach to vulnerable populations with a goal of improving patient outcomes.
# A care practice that includes outreach to vulnerable populations with a goal of improving patient outcomes.
# A patient intake process that is able to leverage all of the patient identification methods.
# A patient intake process that is able to leverage all of the patient identification methods.
# A focus on mobile phone access as the medium of choice.
==foo==
*Users will need a state driver’s license or a state issued ID card plus a Medicaid ID card #.  Two factor authentication can be a SMS #, a biometric or a one-time password OTP. The process details will be shared at a later time.


Regarding the user/patient, their mobile phone/smartphone will be the medium of choice along with a medical facility health kiosk. Users will need a state driver’s license or a state issued ID card plus a Medicaid ID card #.  Two factor authentication can be a SMS #, a biometric or a one-time password OTP. The process details will be shared at a later time.
==References==
==References==
This work is an outgrowth of the Identity Ecosystem Framework – Registry (IDEF-R) which was a work-effort under IDESG which was designed and partially built with funding from the US Department of Commerce NSTIC Program office and administered by NIST. That effort continues is in the Kantara FIRE Work Groups (Federated Identity Resilient Ecosystem) and the Health Identity Assurance. The software is available for demonstration.
This work is an outgrowth of the Identity Ecosystem Framework – Registry (IDEF-R) which was a work-effort under IDESG which was designed and partially built with funding from the US Department of Commerce NSTIC Program office and administered by NIST. That effort continues is in the Kantara FIRE Work Groups (Federated Identity Resilient Ecosystem) and the Health Identity Assurance. The software is available for demonstration.

Revision as of 08:00, 17 May 2020

Full Title

Public Health Centers as a Vulnerable Populations use case of the Identity Ecosystem Framework.

Goals

  1. The patient is reliably matched to their Electronic Health Records (EHR).
  2. The patient is given access to their health information in a secure mannner.
  3. The patient outcomes are improved by easy exchange and monitoring of patient compliance with the care plan.

Context

In context of the Trusted Exchange Framework and Common Agreement (TEFCA), the Sequoia Recognized Coordinating Entity and health information exchanges, there is ongoing dialogue regarding the data sharing agreement, interoperability, electronica health records using FHIR formats. This is a plan for engaging vulnerable populations.

The first challenge is Patient Matching which is a life or death as well as a medication fraud issue. The second challenge is the ONC’s Cures Act Final Rule which makes clear that all Patient Health information needs to be available to patients. Since a large fraction (91%) of the US population at large as well as the vulnerable population have cell phones, this use case will focus on vulnerable patients that have access to a cell phone. The large majority of those are smart phones. When patient outcomes are considered, it may even be cost effective to provide the vulnerable patient with a smart phone. The Cures act explicitly notes that applications provided with smart phones need to be from certified developers and the TEFCA adds the requirement for NIST IAL2 and AAL2 (SP 800-63-3) Identity integrated with HIE’s and record locator services to ensure interoperability and patient safety.

Today that is not a realistic or even an achievable goal for vulnerable populations. What is achievable is that our work group can start to put in place a trusted entity infrastructure for a CSP on-ramp coupled with a trust registry that is linked to a record locator service for the specific purpose of serving a vulnerable population with a user friendly app with core functionality content that is interoperable. And there is a way to incentivize user/patients to want to participate that can increase compliance, quality of life and generate a positive ROI. (The proposal being shared originated with IDESG and this team). The trusted entity, a CSP, issues or registers subscriber authenticators and issues and verifies electronic credentials of subscribers including pseudonymous identity, different levels of assurance and identity, including federations.

Preconditions

  1. A care practice that includes outreach to vulnerable populations with a goal of improving patient outcomes.
  2. A patient intake process that is able to leverage all of the patient identification methods.
  3. A focus on mobile phone access as the medium of choice.

foo

  • Users will need a state driver’s license or a state issued ID card plus a Medicaid ID card #. Two factor authentication can be a SMS #, a biometric or a one-time password OTP. The process details will be shared at a later time.

References

This work is an outgrowth of the Identity Ecosystem Framework – Registry (IDEF-R) which was a work-effort under IDESG which was designed and partially built with funding from the US Department of Commerce NSTIC Program office and administered by NIST. That effort continues is in the Kantara FIRE Work Groups (Federated Identity Resilient Ecosystem) and the Health Identity Assurance. The software is available for demonstration.

References