FHIR IG analytics| Package | hl7.fhir.uv.cmhaffr2 |
| Resource Type | Requirements |
| Id | Requirements-CMHAFFR2-APU.3.json |
| FHIR Version | R5 |
| Source | https://build.fhir.org/ig/HL7/cmhaff-ig/Requirements-CMHAFFR2-APU.3.html |
| URL | http://hl7.org/fhir/uv/cmhaffr2/Requirements/CMHAFFR2-APU.3 |
| Version | 2.0.1 |
| Status | active |
| Date | 2025-05-28T08:01:49+00:00 |
| Name | APU_3_Pairing_or_Syncing_User_Accounts_with_Devices_and_Data_Repositories |
| Title | APU.3 Pairing or Syncing User Accounts with Devices and Data Repositories (Header) |
| Realm | uv |
| Authority | hl7 |
| Description | This category is about consumer verification of all devices to which they wish to pair or sync data. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
This category is about consumer verification of all devices to which they wish to pair or sync data.
| APU.3#77 | SHALL |
User has authenticated identity to an app and has an active session before pairing an external device to an app account. |
| APU.3#78 | SHALL |
Before a device is paired with an app to collect information about a specific individual, the app displays a screen which asks the user to confirm that the device will collect information about a specific, named person. The person may be the account holder or a proxy subject of the account holder. |
| APU.3#79 | SHALL |
The person who pairs a device with an individual in context of use of a specific app can un-pair the device and individual through an app utility function. |
| APU.3#80 | SHALL |
Before a device is paired with an app to collect information about a specific individual, the app states what data will be collected by the device and how the device data is used. This statement may include a link to an informational page which provides details about data collection and use. |
| APU.3#81 | SHALL |
[Data for more than one person can be collected by the app/device pair] The app asks the account holder to confirm the person for whom data will be collected by the device before data is collected and transmitted. |
| APU.3#82 | SHALL |
[Developer includes a syncing option within APP (e.g., same app data synchronized across smartphone and tablet devices)] User is provided with option to consent with syncing process.[1] |
{
"resourceType": "Requirements",
"id": "CMHAFFR2-APU.3",
"meta": {
"profile": [
"http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/FMHeader"
]
},
"text": {
"status": "extensions",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "mobile"
}
],
"url": "http://hl7.org/fhir/uv/cmhaffr2/Requirements/CMHAFFR2-APU.3",
"version": "2.0.1",
"name": "APU_3_Pairing_or_Syncing_User_Accounts_with_Devices_and_Data_Repositories",
"title": "APU.3 Pairing or Syncing User Accounts with Devices and Data Repositories (Header)",
"status": "active",
"date": "2025-05-28T08:01:49+00:00",
"publisher": "HL7 International / Mobile Health",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/mobile"
}
]
}
],
"description": "This category is about consumer verification of all devices to which they wish to pair or sync data.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"statement": [
{
"extension": [
{
"url": "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "CMHAFFR2-APU.3-77",
"label": "APU.3#77",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "User has authenticated identity to an app and has an active session before pairing an external device to an app account."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "CMHAFFR2-APU.3-78",
"label": "APU.3#78",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "Before a device is paired with an app to collect information about a specific individual, the app displays a screen which asks the user to confirm that the device will collect information about a specific, named person. The person may be the account holder or a proxy subject of the account holder."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "CMHAFFR2-APU.3-79",
"label": "APU.3#79",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The person who pairs a device with an individual in context of use of a specific app can un-pair the device and individual through an app utility function."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "CMHAFFR2-APU.3-80",
"label": "APU.3#80",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "Before a device is paired with an app to collect information about a specific individual, the app states what data will be collected by the device and how the device data is used. This statement may include a link to an informational page which provides details about data collection and use."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "CMHAFFR2-APU.3-81",
"label": "APU.3#81",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "[Data for more than one person can be collected by the app/device pair] The app asks the account holder to confirm the person for whom data will be collected by the device before data is collected and transmitted."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "CMHAFFR2-APU.3-82",
"label": "APU.3#82",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "[Developer includes a syncing option within APP (e.g., same app data synchronized across smartphone and tablet devices)] User is provided with option to consent with syncing process.[1]"
}
]
}