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

## : PH.5.4 Integration with Third Party Clinical Decision Support Services (Function) - TTL Representation

Active as of 2024-01-31

Raw ttl | Download

    @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.5.4"] ; #
      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.5.4#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 manage their registration(s) to a third-party clinical decision support service(s) (e.g., the name of the service, the Internet address of the service, the date of the registration, the status of the registration) according to user preference, organizational policy, and/or jurisdictional law. NOTE: The identification of third-party clinical decision support services could be handled either by the PHR Account Holder, the vendor, or both.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.5.4#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 for the PHR Account Holder to tag the PHR-S information that is shared with a third-party clinical decision support service.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.5.4#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 for the PHR Account Holder to render responses to specific structured questions from a third-party clinical decision support service.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.5.4#04</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY provide the ability to analyze problems/conditions (in terms of the onset and/or duration, frequency/pattern, and impact on Activities of Daily Living of the condition/problem) and render findings/issues/alerts to the PHR Account Holder (for possible transmission to a member of the care team) according to user preference, organizational policy, and/or jurisdictional law. The ingredients of this analysis might only appear (collectively) in the PHR Account Holder's PHR. The results of such an analysis could be shared with certain members of the PHR Account Holder's care team for consideration. For example, the PHR Account Holder becomes less physically active and wonders why, the PHR system can analyze the PHR Account Holder's conditions and suggest that the increased amount of joint pain as a possible factor.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.5.4#05</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY provide the ability to analyze medications and therapies that are prescribed by clinicians and render findings/issues/alerts to the PHR Account Holder (for possible transmission to a member of the care team) according to user preference, organizational policy, and/or jurisdictional law. The ingredients of this analysis might only appear (collectively) in the PHR Account Holder's PHR. The results of such an analysis could be shared with certain members of the PHR Account Holder's care team for consideration. For example, the PHR Account Holder begins eating bananas and wonders why the medication being consumed does not seem to be as effective; the PHR system analyzes the nutrient-drug interaction as a possible factor.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.5.4#06</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY provide the ability to analyze exacerbating factors (e.g., environmental or emotional factors) and render findings/issues/alerts to the PHR Account Holder (for possible transmission to a member of the care team) according to user preference, organizational policy, and/or jurisdictional law. The ingredients of this analysis might only appear (collectively) in the PHR Account Holder's PHR. The results of such an analysis could be shared with certain members of the PHR Account Holder's care team for consideration. For example, the PHR Account Holder begins feeling depressed and wonders why; the PHR system analyzes the PHR Account Holder's recent birth of a child as a possible factor.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.5.4#07</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY provide the ability to analyze the nutrients that are consumed and render findings/issues/alerts to the PHR Account Holder (for possible transmission to a member of the care team) according to user preference, organizational policy, and/or jurisdictional law. The ingredients of this analysis might only appear (collectively) in the PHR Account Holder's PHR. The results of such an analysis could be shared with certain members of the PHR Account Holder's care team for consideration. For example, the PHR Account Holder begins eating bananas and wonders why the medication being consumed does not seem to be as effective; the PHR system analyzes the nutrient-drug interaction as a possible factor.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.5.4#08</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY provide the ability to analyze  the genetic profile of the PHR Account Holder and render findings/issues/alerts to the PHR Account Holder (for possible transmission to a member of the care team) according to user preference, organizational policy, and/or jurisdictional law. The ingredients of this analysis might only appear (collectively) in the PHR Account Holder's PHR. The results of such an analysis could be shared with certain members of the PHR Account Holder's care team for consideration. For example, the PHR Account Holder begins to feel sluggish and wonders why; the PHR system analyzes the PHR Account Holder's genetic profile and offers sickle cell anemia as a possible factor.</p>\n</div></span>\n                \n\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>PH.5.4#09</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\">\n                \n                <span>MAY</span>\n                \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                \n                <span><div><p>The system MAY render an alert or notification to certain members of the PHR Account Holder's care team regarding the results of problem/condition analyses (including the components of those analyses) according to user preference, organizational policy, and/or jurisdictional law.</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.5.4"^^xsd:anyURI] ; #
      fhir:version [ fhir:v "0.1.0"] ; #
      fhir:name [ fhir:v "PH_5_4_Integration_with_Third_Party_Clinical_Decision_Support_Services"] ; #
      fhir:title [ fhir:v "PH.5.4 Integration with Third Party Clinical Decision Support Services (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 "A variety of clinical decision support services are currently available for professional use; a growing number of these services are becoming available for lay use. The primarily focus of these services is to assist with making an assessment and then recommending a treatment protocol.\r\n\r\nExample(s): Provide access to clinical decision support services that provide differential diagnoses and advice for further management for common complaints such as sore throat or cough."] ; #
      fhir:statement ( [
    fhir:key [ fhir:v "PHRSFMR2-PH.5.4-01" ] ;
    fhir:label [ fhir:v "PH.5.4#01" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD provide the ability for the PHR Account Holder to manage their registration(s) to a third-party clinical decision support service(s) (e.g., the name of the service, the Internet address of the service, the date of the registration, the status of the registration) according to user preference, organizational policy, and/or jurisdictional law. NOTE: The identification of third-party clinical decision support services could be handled either by the PHR Account Holder, the vendor, or both." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.5.4-02" ] ;
    fhir:label [ fhir:v "PH.5.4#02" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD provide the ability for the PHR Account Holder to tag the PHR-S information that is shared with a third-party clinical decision support service." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.5.4-03" ] ;
    fhir:label [ fhir:v "PH.5.4#03" ] ;
        ( fhir:conformance [ fhir:v "SHOULD" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system SHOULD provide the ability for the PHR Account Holder to render responses to specific structured questions from a third-party clinical decision support service." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.5.4-04" ] ;
    fhir:label [ fhir:v "PH.5.4#04" ] ;
        ( fhir:conformance [ fhir:v "MAY" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system MAY provide the ability to analyze problems/conditions (in terms of the onset and/or duration, frequency/pattern, and impact on Activities of Daily Living of the condition/problem) and render findings/issues/alerts to the PHR Account Holder (for possible transmission to a member of the care team) according to user preference, organizational policy, and/or jurisdictional law. The ingredients of this analysis might only appear (collectively) in the PHR Account Holder's PHR. The results of such an analysis could be shared with certain members of the PHR Account Holder's care team for consideration. For example, the PHR Account Holder becomes less physically active and wonders why, the PHR system can analyze the PHR Account Holder's conditions and suggest that the increased amount of joint pain as a possible factor." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.5.4-05" ] ;
    fhir:label [ fhir:v "PH.5.4#05" ] ;
        ( fhir:conformance [ fhir:v "MAY" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system MAY provide the ability to analyze medications and therapies that are prescribed by clinicians and render findings/issues/alerts to the PHR Account Holder (for possible transmission to a member of the care team) according to user preference, organizational policy, and/or jurisdictional law. The ingredients of this analysis might only appear (collectively) in the PHR Account Holder's PHR. The results of such an analysis could be shared with certain members of the PHR Account Holder's care team for consideration. For example, the PHR Account Holder begins eating bananas and wonders why the medication being consumed does not seem to be as effective; the PHR system analyzes the nutrient-drug interaction as a possible factor." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.5.4-06" ] ;
    fhir:label [ fhir:v "PH.5.4#06" ] ;
        ( fhir:conformance [ fhir:v "MAY" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system MAY provide the ability to analyze exacerbating factors (e.g., environmental or emotional factors) and render findings/issues/alerts to the PHR Account Holder (for possible transmission to a member of the care team) according to user preference, organizational policy, and/or jurisdictional law. The ingredients of this analysis might only appear (collectively) in the PHR Account Holder's PHR. The results of such an analysis could be shared with certain members of the PHR Account Holder's care team for consideration. For example, the PHR Account Holder begins feeling depressed and wonders why; the PHR system analyzes the PHR Account Holder's recent birth of a child as a possible factor." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.5.4-07" ] ;
    fhir:label [ fhir:v "PH.5.4#07" ] ;
        ( fhir:conformance [ fhir:v "MAY" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system MAY provide the ability to analyze the nutrients that are consumed and render findings/issues/alerts to the PHR Account Holder (for possible transmission to a member of the care team) according to user preference, organizational policy, and/or jurisdictional law. The ingredients of this analysis might only appear (collectively) in the PHR Account Holder's PHR. The results of such an analysis could be shared with certain members of the PHR Account Holder's care team for consideration. For example, the PHR Account Holder begins eating bananas and wonders why the medication being consumed does not seem to be as effective; the PHR system analyzes the nutrient-drug interaction as a possible factor." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.5.4-08" ] ;
    fhir:label [ fhir:v "PH.5.4#08" ] ;
        ( fhir:conformance [ fhir:v "MAY" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system MAY provide the ability to analyze  the genetic profile of the PHR Account Holder and render findings/issues/alerts to the PHR Account Holder (for possible transmission to a member of the care team) according to user preference, organizational policy, and/or jurisdictional law. The ingredients of this analysis might only appear (collectively) in the PHR Account Holder's PHR. The results of such an analysis could be shared with certain members of the PHR Account Holder's care team for consideration. For example, the PHR Account Holder begins to feel sluggish and wonders why; the PHR system analyzes the PHR Account Holder's genetic profile and offers sickle cell anemia as a possible factor." ]
      ] [
    fhir:key [ fhir:v "PHRSFMR2-PH.5.4-09" ] ;
    fhir:label [ fhir:v "PH.5.4#09" ] ;
        ( fhir:conformance [ fhir:v "MAY" ] ) ;
    fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
    fhir:requirement [ fhir:v "The system MAY render an alert or notification to certain members of the PHR Account Holder's care team regarding the results of problem/condition analyses (including the components of those analyses) according to user preference, organizational policy, and/or jurisdictional law." ]
      ] ) . #