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 |
@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
# - resource -------------------------------------------------------------------
a fhir:Requirements ;
fhir:nodeRole fhir:treeRoot ;
fhir:id [ fhir:v "PHRSFMR2-PH.6.3"] ; #
fhir:meta [
( fhir:profile [
fhir:v "http://hl7.org/ehrs/StructureDefinition/FMFunction"^^xsd:anyURI ;
fhir:link <http://hl7.org/ehrs/StructureDefinition/FMFunction> ] )
] ; #
fhir:text [
fhir:status [ fhir:v "extensions" ] ;
fhir: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>PH.6.3#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture and maintain communications between providers and the PHR Account Holder and/or the PHR Account Holder's Proxy according to organizational policy and/or jurisdictional law.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#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 provide the ability to manage scanned documents based on the document type (e.g., based on the quality, format, origin, completion status, or intended diagnostic use (e.g., a screening versus a diagnostic breast examination)).</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#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 and maintain communications (e.g., date, entity, or details of communication) that were originated by the PHR Account Holder or Authorized PHR User.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture, maintain and render PHR authorization information (e.g., to support a designee's claim that the designee is authorized to receive PHR Account Holder-related health information).</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#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 render to the PHR Account Holder a notification of the arrival of a provider-originated communication.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#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 exchange communications between providers and PHR Account Holders using a secure connection.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to PH.6.3 (Communication Between Provider and PHR Account Holder and/or the PHR Account Holder's Representative) in order to exchange information.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to TI.1.8 (Patient Privacy and Confidentiality) to support adherence to various levels of confidentiality when exchanging information.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#09</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 tag a set of elements within the PHR Account Holder's self-generated care plan that the PHR Account Holder intends to send to selected care team members.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#10</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>IF the PHR Account Holder is creating a self-generated care plan, THEN the system SHOULD provide the ability for the PHR Account Holder to tag a set of selected care team members (to whom the PHR Account Holder intends to send certain information).</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.3#11</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 transmit a tagged set of elements within the PHR Account Holder's self-generated care plan to a tagged set of selected care team members.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n </table>\n</div>"
] ; #
fhir:url [ fhir:v "http://hl7.org/ehrs/Requirements/PHRSFMR2-PH.6.3"^^xsd:anyURI] ; #
fhir:version [ fhir:v "0.1.0"] ; #
fhir:name [ fhir:v "PH_6_3_Communications_Between_Provider_and_PHR_Account_Holder_and_or_PHR_Account_Holder_Proxy"] ; #
fhir:title [ fhir:v "PH.6.3 Communications Between Provider and PHR Account Holder and/or PHR Account Holder Proxy (Function)"] ; #
fhir:status [ fhir:v "active"] ; #
fhir:date [ fhir:v "2024-01-31T14:45:34+00:00"^^xsd:dateTime] ; #
fhir:publisher [ fhir:v "EHR WG"] ; #
fhir:contact ( [
( fhir:telecom [
fhir:system [ fhir:v "url" ] ;
fhir:value [ fhir:v "http://www.hl7.org/Special/committees/ehr" ] ] )
] ) ; #
fhir:description [ fhir:v "The PHR Account Holder may fulfill specific requests for data or obtain requested diagnostic studies prior to the formal encounter. This may include providing PHR-S access to the new provider. The provider could also communicate with various members of the PHR Account Holder's care team.\r\n\r\nExample(s): The PHR Account Holder MAY fill out a current Review Of Systems (ROS) template questionnaire and specific chief complaint related questions as part of the History of Present Illness (HPI) prior to the encounter."] ; #
fhir:statement ( [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-01" ] ;
fhir:label [ fhir:v "PH.6.3#01" ] ;
( fhir:conformance [ fhir:v "SHALL" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system SHALL provide the ability to capture and maintain communications between providers and the PHR Account Holder and/or the PHR Account Holder's Proxy according to organizational policy and/or jurisdictional law." ]
] [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-02" ] ;
fhir:label [ fhir:v "PH.6.3#02" ] ;
( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system SHOULD provide the ability to manage scanned documents based on the document type (e.g., based on the quality, format, origin, completion status, or intended diagnostic use (e.g., a screening versus a diagnostic breast examination))." ]
] [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-03" ] ;
fhir:label [ fhir:v "PH.6.3#03" ] ;
( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system SHOULD provide the ability to capture and maintain communications (e.g., date, entity, or details of communication) that were originated by the PHR Account Holder or Authorized PHR User." ]
] [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-04" ] ;
fhir:label [ fhir:v "PH.6.3#04" ] ;
( fhir:conformance [ fhir:v "SHALL" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system SHALL provide the ability to capture, maintain and render PHR authorization information (e.g., to support a designee's claim that the designee is authorized to receive PHR Account Holder-related health information)." ]
] [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-05" ] ;
fhir:label [ fhir:v "PH.6.3#05" ] ;
( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system SHOULD render to the PHR Account Holder a notification of the arrival of a provider-originated communication." ]
] [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-06" ] ;
fhir:label [ fhir:v "PH.6.3#06" ] ;
( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system SHOULD provide the ability to exchange communications between providers and PHR Account Holders using a secure connection." ]
] [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-07" ] ;
fhir:label [ fhir:v "PH.6.3#07" ] ;
( fhir:conformance [ fhir:v "SHALL" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system SHALL conform to PH.6.3 (Communication Between Provider and PHR Account Holder and/or the PHR Account Holder's Representative) in order to exchange information." ]
] [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-08" ] ;
fhir:label [ fhir:v "PH.6.3#08" ] ;
( fhir:conformance [ fhir:v "SHALL" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system SHALL conform to TI.1.8 (Patient Privacy and Confidentiality) to support adherence to various levels of confidentiality when exchanging information." ]
] [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-09" ] ;
fhir:label [ fhir:v "PH.6.3#09" ] ;
( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system SHOULD provide the ability to tag a set of elements within the PHR Account Holder's self-generated care plan that the PHR Account Holder intends to send to selected care team members." ]
] [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-10" ] ;
fhir:label [ fhir:v "PH.6.3#10" ] ;
( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v "true"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "IF the PHR Account Holder is creating a self-generated care plan, THEN the system SHOULD provide the ability for the PHR Account Holder to tag a set of selected care team members (to whom the PHR Account Holder intends to send certain information)." ]
] [
fhir:key [ fhir:v "PHRSFMR2-PH.6.3-11" ] ;
fhir:label [ fhir:v "PH.6.3#11" ] ;
( fhir:conformance [ fhir:v "SHOULD" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system SHOULD provide the ability to transmit a tagged set of elements within the PHR Account Holder's self-generated care plan to a tagged set of selected care team members." ]
] ) . #
IG © 2023 EHR WG. Package hl7.phrsfmr2.base#0.1.0 based on FHIR 5.0.0. Generated 2024-01-31
Links: Table of Contents |
QA Report