Application Data Exchange Assessment Framework and Functional Requirements for Mobile Health
0.1.0 - STU 1 Ballot

This page is part of the Application Data Exchange Assessment Framework and Functional Requirements for Mobile Health (v0.1.0: STU 1 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

Sharing Mechanism

The Sharing Mechanism category ensures that sharing is possible and that the mechanism is described.

Feature: A System Must Support Either Push or Pull Sharing.

NOTE: Reference to third party components can be made in evaluation of this requirement. In cases when a system supports storage in a third party component that enables push or pull sharing, and that third party component supports push or pull sharing, the system also supports it. The system documentation must reference the third party component (e.g., by product name) and then the documentation for that third party component can be evaluted. Apple HealthKit and Google Health are examples of such third party (mobile operating system) components that provide such capabilities.

Scenario: Sharing

GIVEN
a <System>
WHEN
when the <Documentation> for <System> is reviewed
THEN
there is a documented method for push or pull sharing in <Documentation>

Feature: The System Should be Able to Push New Data to Another Party That the User Has Shared With.

Scenario: Push Sharing

GIVEN
a <System> supporting push sharing
AND
a <User>
AND
a <Party> the user has shared with
WHEN
new <Data> for <User> has been collected
THEN
it is sent to <Party>

Feature: Other Parties That the User Has Shared With Should be Able to Pull Data From the System.

Scenario: Pull Sharing

GIVEN
a <System> supporting pull sharing
AND
a <User>
AND
a <Party> the user has shared with
WHEN
new <Data> for <User> has been collected
THEN
it can be retrieved by <Party>