This page is part of the xShare Project Yellow Button Implementation Guide (v0.1.0: Release 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
The application domain describes what are the logical (software) components involved in the yellow button business processes and how they interact, collaborate or are coordinated.
In this version a sequence diagram is used to describe how - from an application perspective - the business process is realized.
The download functionality enables the citizen to download their health data (in the EEHRxF machine readable format and optionally also human readable format, e.g., PDF) with a click-of-a-button, from a health provider portal/app to their computer or smartphone, according to the following workflow:
One-time share
The one-time share (consent) functionality enables the citizen to consent and share their health data (in the EEHRxF) with a click-of-a-button, from a health provider portal/app to a trusted one (e.g., healthcare provider, relative, or a third-party health app), according to the following workflow:
Linked option
The linked option functionality enables the citizen to share their health data (in the EEHRxF) with a click-of-a-button, from a health provider portal/app to a trusted one (e.g., healthcare provider, relative, clinical trials, research institutions) for a period of time, according to the following workflow:
Declare and Prove Your Compliance
Claim Your Compliance
To claim compliance the application level rules specified in this page, xShare Yellow Button implementers must issue a conformance statement in accordance with the indications of the Claim Your Conformance section.
Prove Your Compliance
To prove compliance the application level rules specified in this page, xShare Yellow Button implementers must be able to demostrate that thier solutions are conformant with what is specified in the
Prove Your Conformance section.