Health Care Native Application - Revision history

Tom: /* References */

2023-10-25T19:21:21Z

‎References

Tom: /* References */

2023-10-25T19:20:39Z

‎References

Tom: /* References */

2022-09-22T22:49:30Z

‎References

Tom: /* Problems */

2022-09-22T20:54:19Z

‎Problems

Tom: /* Actors */

2022-09-22T20:52:33Z

‎Actors

Tom: /* Scenarios / User Journeys */

2019-07-16T00:03:41Z

‎Scenarios / User Journeys

Tom: /* Scenarios / User Journeys */

2019-07-15T23:58:42Z

‎Scenarios / User Journeys

Tom: /* Scenarios / User Journeys */

2019-07-15T23:55:53Z

‎Scenarios / User Journeys

Tom: /* Scenarios / User Journeys */

2019-07-15T22:30:54Z

‎Scenarios / User Journeys

Tom: /* Results */

2019-07-12T17:04:34Z

‎Results

@@ Line 109: / Line 109: @@
 <references />
 * Some of the details on this page are proprietary or covered by US patents.
 [[Category: Use Case]]
 [[Category: Health]]
 [[Category: Attestation]]

@@ Line 110: / Line 110: @@
 <references />
 * Some of the details on this page are proprietary or covered by US patents.
-[[Category:Use Case]]
+[[Category: Use Case]]
-[[Category:Health]]
+[[Category: Health]]

@@ Line 107: / Line 107: @@
 ==References==
 * Some of the details on this page are proprietary or covered by US patents.
 [[Category:Use Case]]
 [[Category:Health]]

@@ Line 27: / Line 27: @@
 ==Problems==
-Privacy of Health data is not protected by HIPAA when it leaves the medical center into the patient's custody.  The US Congress has a bill before it that is so popular that it was voted out of committee by 53-2.<ref>Matt Laslo, ''The Shaky Future of a Post-Roe Federal Privacy Law'' Wired (2022-09-15) https://www.wired.com/story/adppa-roe-democrats-congress/</ref> The two negative votes were state of California Democrats that wanted existing California law to remain in effect as it was more restrictive. Since the leader of the House, Nancy Pelosi, is also from California, action on the bill is not likely.
+Privacy of Health data is not protected by HIPAA when it leaves the medical center into the patient's custody.  The US Congress has a bill before it that is so popular that it was voted out of committee by 53-2.<ref>Matt Laslo, ''The Shaky Future of a Post-Roe Federal Privacy Law'' Wired (2022-09-15) https://www.wired.com/story/adppa-roe-democrats-congress/</ref> The two negative votes were state of California Democrats that wanted existing California law to remain in effect as it was more restrictive. Since the leader of the House, Nancy Pelosi, is also from California, action on the bill is not likely.<blockquote>“At the end of the day, this is not HIPAA-protected,” Congresswoman Raja Krishnamoorthi of Illinois says of the health-related data collected by many apps. The Democrat serves on the Oversight Committee and is a part of an investigation looking into what health apps do with women’s data. This May, a study by JMIR Mhealth Uhealth examined the 23 most popular women’s mHealth apps and found 61 percent relied on geolocators, while only 52 percent even asked for users’ consent. A full 87 percent—20 of 23 tested—“shared user data with third parties.” The other three apps didn’t provide any information on data-sharing.</blockquote>
 ==Preconditions==

@@ Line 25: / Line 25: @@
 #Trusted Provider of services related to [[Authentication]] or [[Patient Credential]] sharing.
 #[[Credential Service Provider]] is the role that determines that the patient has established an IAL2 authentication method.
 ==Preconditions==

@@ Line 66: / Line 66: @@
 # A patient will be able to add or delete any contact at any time.
 # Any contact is able to accept or reject a request to include them in the record. (Default is accept.) If these contacts do not include medical directives in their record, then IAL1 authentication will be sufficient for them to update their information.
-# All of this information is available on [[FirstNet]] to authorized Responders.
+# All of this information is available on [[FirstNet]] to authorized First Responders.
 Journey 6 - The patient visits some other [[Web Site]] associated with (eg) a specialist with a referral from the PCP.

@@ Line 59: / Line 59: @@
 # Subsequent visits to the [[EHR]] with the data from the PCP will work with only local [[Authentication]] of the user to the [[Native App]] (with the help of the phone's operating system.)
-Journey 5 - The patient or the PCP wants to use the [[Trust Third Party]] from Journey 4 as storage for
+Journey 5 - The patient or the PCP wants to use the [[Trusted Third Party]] (TTP) from Journey 4 as storage for [[User Owned Information]]. In other words, information provided by the user that they can change on their own initiative. In most cases the information does not need a doctors approval, but some patient directives do need approval.
 Journey 6 - The patient visits some other [[Web Site]] associated with (eg) a specialist with a referral from the PCP.

@@ Line 59: / Line 59: @@
 # Subsequent visits to the [[EHR]] with the data from the PCP will work with only local [[Authentication]] of the user to the [[Native App]] (with the help of the phone's operating system.)
-Journey 5 - The patient visits some other [[Web Site]] associated with (eg) a specialist with a referral from the PCP.
+Journey 5 - The patient or the PCP wants to use the [[Trust Third Party]] from Journey 4 as storage for
 # The most difficult case is where the patient has on gone through [[Identity Proofing]] at the specialist, but want to see the [[EHR]] at the specialist's web site.
 # When accessing the specialist's [[Web Site]] the browser on the patient's web sites recognizes the identifier from the specialist and redirects the user to the [[Native App]]. This identifier will have a prefix that enables this recognition.
@@ Line 67: / Line 69: @@
 # If both the specialist's [[Web Site]] and the [[Native App]] are agreed that each is trustworthy, the patient will be able to upload [[PHI]] to the specialist's [[Web Site]].
-Journey 6 - The patient is unwilling to accept the site's conditions, or the site is unwilling to accept the user's stipulations. No sharing of patient data is possible.
+Journey 7 - The patient is unwilling to accept the site's conditions, or the site is unwilling to accept the user's stipulations. No sharing of patient data is possible.
 ==Results==

@@ Line 79: / Line 79: @@
 #No data is ever shared with any provider that has not been strongly identified to the user.
 #The user results are available it is assumed that the consent receipt acknowledged that the data would be sent back to the primary care doctor.
 Examples: