Medical Records Identifier - Revision history

Tom: /* Privacy Considerations */

2019-04-19T00:48:52Z

‎Privacy Considerations

2019-04-19T00:44:07Z

‎Solutions

2019-03-21T17:28:17Z

‎Universal Identifier Resolver

2019-03-21T17:23:38Z

‎Universal Identifier Resolver

2019-02-01T23:30:51Z

‎Miscellaneous References

2019-02-01T23:30:17Z

‎Miscellaneous References

2019-01-25T00:21:08Z

‎Miscellaneous References

2018-12-22T18:09:54Z

‎Universal Identifier Resolver

2018-12-22T18:04:30Z

‎Problems

2018-12-22T17:53:22Z

‎Problems

@@ Line 34: / Line 34: @@
 ===Privacy Considerations===
-In the US all medical records are protected by [[HIPPA]] regulations which strictly limit who can have access. This consideration will require strong identifiers for any user that wants to access their medical records. At the same time it is important to provide [[Exceptional Access]] to first responders who need information quickly, even in cases where the patient is unable to provide [[User Consent]].
+In the US all medical records are protected by [[https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html HIPAA regulations]] which strictly limit who can have access. This consideration will require strong identifiers for any user that wants to access their medical records. At the same time it is important to provide [[Exceptional Access]] to first responders who need information quickly, even in cases where the patient is unable to provide [[User Consent]].
 ===1 Well-known Patients===

@@ Line 32: / Line 32: @@
 *[[Authentication]] will be provided for any [[Medical Records Identifier]]. The exact relationship between the authenticator and the resolver is TBD.
 *It is important that all of the records under a single [[Medical Records Identifier]] are associated with one unique human being. It is understood that errors will happen with assignments of records to [[Medical Records Identifier]]s and the some robust recovery and redress procedures are in place to correct errors; including errors reported by the user.
 ===1 Well-known Patients===

@@ Line 27: / Line 27: @@
 ==Solutions==
-===Universal Identifier Resolver===
+===Medical Records Locator Service===
-While the Universal Identifier Resolver should be applicable to any complex [[Identity Ecosystem]], in the medical arena it can function as a medical records locator. It's purpose is to return pointers to data records and not the data contained in those records. The following are the changes that are needed for this concept to be successful in the medical arena in the US, or any other [[Distributed ID]] [[Ecosystem]].
+While a Universal Identifier Resolver should be applicable to any complex [[Identity Ecosystem]], in the medical arena it can function as a medical records locator. It's purpose is to return pointers to data records and not the data contained in those records. The following are the changes that are needed for this concept to be successful in the medical arena in the US, or any other [[Distributed ID]] [[Ecosystem]].
 *The US medical community accepts the idea that any licensed and registered health care provider can query a [[Universal Resolver]] with a user's Identifier and get a response with data appropriate to their need and authority within 2 minutes for emergency care and within 2 hours for more detailed records. Note that the resolver does not need to be a records provider.
 *[[Authentication]] will be provided for any [[Medical Records Identifier]]. The exact relationship between the authenticator and the resolver is TBD.

@@ Line 28: / Line 28: @@
 ==Solutions==
 ===Universal Identifier Resolver===
-While the Universal Identifier Resolver should be applicable to any complex [[Identity Ecosystem]], in the medical arena it can function as a medical records locator. It's purpose is to return pointers to data records and not the data contained in those records. The following are the changes that are needed for this concept to be successful in the medical arena in the US, or any other [[Distributed Identifier]] [[Ecosystem]].
+While the Universal Identifier Resolver should be applicable to any complex [[Identity Ecosystem]], in the medical arena it can function as a medical records locator. It's purpose is to return pointers to data records and not the data contained in those records. The following are the changes that are needed for this concept to be successful in the medical arena in the US, or any other [[Distributed ID]] [[Ecosystem]].
 *The US medical community accepts the idea that any licensed and registered health care provider can query a [[Universal Resolver]] with a user's Identifier and get a response with data appropriate to their need and authority within 2 minutes for emergency care and within 2 hours for more detailed records. Note that the resolver does not need to be a records provider.
 *[[Authentication]] will be provided for any [[Medical Records Identifier]]. The exact relationship between the authenticator and the resolver is TBD.

@@ Line 50: / Line 50: @@
 ===Miscellaneous References===
 * [https://wiki.idesg.org/wiki/index.php/Health_Care_Profile Health Care Profile] in Kartara IDEF documentation.
-* [[Resolver]] wiki page.
+* [[Trusted Resolver]] wiki page.
 [[Category:Glossary]]
 [[Category:Identifier]]
 [[Category:Health]]

@@ Line 24: / Line 24: @@
 ==Problems==
 * The big problem with any sort of [[Self-issued Identifier]] is [[Trust]] where there are no standards or examples of any trust without a history of trusted behavior.
-* Medical records are known to be riddled with errors today, a situation which will not change soon.<ref>Christina Farr, ''This patient's medical record said she'd given birth twice — in fact, she'd never been pregnant.'' *2018-12-09) CNBC https://www.cnbc.com/2018/12/09/medical-record-errors-common-hard-to-fix.html</ref>
+* Medical records are known to be riddled with errors today, a situation which will not change soon.<ref>Christina Farr, ''This patient's medical record said she'd given birth twice — in fact, she'd never been pregnant.'' (2018-12-09) CNBC https://www.cnbc.com/2018/12/09/medical-record-errors-common-hard-to-fix.html</ref>
 ==Solutions==