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-TI.10.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>TI.10.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 manage data using clinical model maps which may be provided by mapping services (internal or external).</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.10.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 update clinical model maps using standard clinical model services (internal or external).</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.10.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 render data quality and technical quality reports for a user to determine the validity of clinical model mappings using approved mapping techniques.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.10.3#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 for a user to maintain custom clinical model maps using approved mapping techniques where formal standard clinical model maps are unavailable.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.10.3#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 for a user to maintain custom clinical model maps to formal standard clinical model maps in order to support historical data use.</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-TI.10.3"^^xsd:anyURI] ; #
fhir:version [ fhir:v "0.1.0"] ; #
fhir:name [ fhir:v "TI_10_3_Clinical_Model_Mapping"] ; #
fhir:title [ fhir:v "TI.10.3 Clinical Model Mapping (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 ability to map or translate one clinical model to another is fundamental to an organization in an environment where several clinical models are in play to meet different purposes. It is a common occurrence that data is captured using one clinical model, but is shared using another clinical model."] ; #
fhir:statement ( [
fhir:key [ fhir:v "PHRSFMR2-TI.10.3-01" ] ;
fhir:label [ fhir:v "TI.10.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 manage data using clinical model maps which may be provided by mapping services (internal or external)." ]
] [
fhir:key [ fhir:v "PHRSFMR2-TI.10.3-02" ] ;
fhir:label [ fhir:v "TI.10.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 update clinical model maps using standard clinical model services (internal or external)." ]
] [
fhir:key [ fhir:v "PHRSFMR2-TI.10.3-03" ] ;
fhir:label [ fhir:v "TI.10.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 render data quality and technical quality reports for a user to determine the validity of clinical model mappings using approved mapping techniques." ]
] [
fhir:key [ fhir:v "PHRSFMR2-TI.10.3-04" ] ;
fhir:label [ fhir:v "TI.10.3#04" ] ;
( fhir:conformance [ fhir:v "MAY" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system MAY provide the ability for a user to maintain custom clinical model maps using approved mapping techniques where formal standard clinical model maps are unavailable." ]
] [
fhir:key [ fhir:v "PHRSFMR2-TI.10.3-05" ] ;
fhir:label [ fhir:v "TI.10.3#05" ] ;
( fhir:conformance [ fhir:v "MAY" ] ) ;
fhir:conditionality [ fhir:v "false"^^xsd:boolean ] ;
fhir:requirement [ fhir:v "The system MAY provide the ability for a user to maintain custom clinical model maps to formal standard clinical model maps in order to support historical data use." ]
] ) . #
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