Personal Health Record System Functional Model, Release 2
0.1.0 - CI Build
Personal Health Record System Functional Model, Release 2 - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-01-31 |
{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-S.4.1.2",
"meta" : {
"profile" : [
🔗 "http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.1.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>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.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.1.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD capture the source and date of a request for de-identified data.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.1.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture the date of transmission, data transmitted, and the target of the de-identified data.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.1.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture confirmation of the target’s receipt of the data.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.1.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render the history of data transmissions.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.1.2#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to de-identify data according to organizational policy and/or jurisdictional law.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/PHRSFMR2-S.4.1.2",
"version" : "0.1.0",
"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" : "2024-01-31T14:45:34+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "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" : [
{
"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."
},
{
"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."
},
{
"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."
},
{
"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."
},
{
"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."
},
{
"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."
}
]
}