-
Type:
Change Request
-
Resolution: Not Persuasive
-
Priority:
Highest
-
US CARIN Blue Button (FHIR)
-
0.1 [deprecated]
-
Financial Mgmt
-
(NA)
-
onsumer-Directed Payer Data Exchange
-
-
Mark Roberts/ Pat Taylor: 17-0-0
H.Resources (Use Case). To determine what kind of data should be included, the use case should provide a reason why the patient/patient rep. is downloading the data. The way you have worded the use case, it sounds like their primary intent is to invoke their right to the data. As a consumer, I don't think that people would typically download the data just for the sake of it. We might download data because our insurance company has questioned something or requires documentation. In that case the data that we want is really for the insurance company with their arcane codes. We might download data because we , as patient or consumer, might want to review the date for our own purposes. In that case, we might want something besides financial codes.
Existing Wording:
Consumer authorizes the application to access their digital claims data (thereby invoking their Individual Right of Access under HIPAA) via the SMART on FHIR authorization flow
- is voted on by
-
BALLOT-12346 Affirmative - Ruth Berge : 2020-Feb-BLUEBUTTON R1 STU
- Balloted
- relates to
-
FHIR-24838 Use Cases should have a diagram
-
- Published
-
-
FHIR-26649 EOB examples for primary/secondary situation
-
- Published
-
-
FHIR-28168 Clarify that Consent Management is Out of Scope for this IG
-
- Resolved - No Change
-