Package | hl7.ehrs.uv.phrsfmr2 |
Type | Requirements |
Id | PHRSFMR2-S.4.1.2 |
FHIR Version | R5 |
Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-S.4.1.2.html |
URL | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.4.1.2 |
Version | 2.0.1-ballot |
Status | active |
Date | 2025-04-03T15:15:30+00:00 |
Name | S_4_1_2_Manage_De_Identified_Data_Request_Process |
Title | S.4.1.2 Manage De-Identified Data Request Process (Function) |
Authority | hl7 |
Description | Provide PHR Account Holder data in a manner that meets local requirements for de-identification. |
Purpose | When the PHR Account Holder desires to share his/her information in a de-identified state, the PHR Account Holder can export the data in a fashion that meets requirements for de-identification in that locale or realm. Example(s): If a person wants to participate in a study that will utilize de-identified data, then the system should provide the ability to de-identify this data according to the requirements of the study. In Germany, when a PHR Account Holder’s subscription is cancelled, the PHR data may be maintained. But if the data is maintained, it must be maintained in a de-identified state or be pseudonymized (similar to the limited data set in the U.S. Privacy Rule). |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Provide PHR Account Holder data in a manner that meets local requirements for de-identification.
When the PHR Account Holder desires to share his/her information in a de-identified state, the PHR Account Holder can export the data in a fashion that meets requirements for de-identification in that locale or realm.
Example(s): If a person wants to participate in a study that will utilize de-identified data, then the system should provide the ability to de-identify this data according to the requirements of the study.
In Germany, when a PHR Account Holder’s subscription is cancelled, the PHR data may be maintained. But if the data is maintained, it must be maintained in a de-identified state or be pseudonymized (similar to the limited data set in the U.S. Privacy Rule).
S.4.1.2#01 | SHOULD |
The system SHOULD provide the ability for the PHR Account Holder to de-identify his or her information as needed to meet the requirements of a study or other request. |
S.4.1.2#02 | SHOULD |
The system SHOULD capture the source and date of a request for de-identified data. |
S.4.1.2#03 | SHOULD |
The system SHOULD provide the ability to capture the date of transmission, data transmitted, and the target of the de-identified data. |
S.4.1.2#04 | SHOULD |
The system SHOULD provide the ability to capture confirmation of the target’s receipt of the data. |
S.4.1.2#05 | SHOULD |
The system SHOULD provide the ability to render the history of data transmissions. |
S.4.1.2#06 | dependent SHOULD |
The system SHOULD provide the ability to de-identify data according to organizational policy and/or jurisdictional law. |
{ "resourceType": "Requirements", "id": "PHRSFMR2-S.4.1.2", "meta": { "profile": [ "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction" ] }, "text": { "status": "extensions", "div": "<!-- snip (see above) -->" }, "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg", "valueCode": "ehr" } ], "url": "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.4.1.2", "version": "2.0.1-ballot", "name": "S_4_1_2_Manage_De_Identified_Data_Request_Process", "title": "S.4.1.2 Manage De-Identified Data Request Process (Function)", "status": "active", "date": "2025-04-03T15:15:30+00:00", "publisher": "EHR WG", "contact": [ { "telecom": [ { "system": "url", "value": "http://www.hl7.org/Special/committees/ehr" } ] } ], "description": "Provide PHR Account Holder data in a manner that meets local requirements for de-identification.", "purpose": "When the PHR Account Holder desires to share his/her information in a de-identified state, the PHR Account Holder can export the data in a fashion that meets requirements for de-identification in that locale or realm.\r\n\r\nExample(s): If a person wants to participate in a study that will utilize de-identified data, then the system should provide the ability to de-identify this data according to the requirements of the study.\r\n\r\nIn Germany, when a PHR Account Holder’s subscription is cancelled, the PHR data may be maintained. But if the data is maintained, it must be maintained in a de-identified state or be pseudonymized (similar to the limited data set in the U.S. Privacy Rule).", "statement": [ { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": false } ], "key": "PHRSFMR2-S.4.1.2-01", "label": "S.4.1.2#01", "conformance": [ "SHOULD" ], "conditionality": false, "requirement": "The system SHOULD provide the ability for the PHR Account Holder to de-identify his or her information as needed to meet the requirements of a study or other request." }, { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": false } ], "key": "PHRSFMR2-S.4.1.2-02", "label": "S.4.1.2#02", "conformance": [ "SHOULD" ], "conditionality": false, "requirement": "The system SHOULD capture the source and date of a request for de-identified data." }, { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": false } ], "key": "PHRSFMR2-S.4.1.2-03", "label": "S.4.1.2#03", "conformance": [ "SHOULD" ], "conditionality": false, "requirement": "The system SHOULD provide the ability to capture the date of transmission, data transmitted, and the target of the de-identified data." }, { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": false } ], "key": "PHRSFMR2-S.4.1.2-04", "label": "S.4.1.2#04", "conformance": [ "SHOULD" ], "conditionality": false, "requirement": "The system SHOULD provide the ability to capture confirmation of the target’s receipt of the data." }, { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": false } ], "key": "PHRSFMR2-S.4.1.2-05", "label": "S.4.1.2#05", "conformance": [ "SHOULD" ], "conditionality": false, "requirement": "The system SHOULD provide the ability to render the history of data transmissions." }, { "extension": [ { "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent", "valueBoolean": true } ], "key": "PHRSFMR2-S.4.1.2-06", "label": "S.4.1.2#06", "conformance": [ "SHOULD" ], "conditionality": false, "requirement": "The system SHOULD provide the ability to de-identify data according to organizational policy and/or jurisdictional law." } ] }