Publish Box goes here

• Narrative Content
• XML
• JSON
• TTL

: AS.7 Support Encounter/Episode of Care Management (Header) - TTL Representation

Active as of 2024-08-12

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 "EHRSFMR2.1-AS.7"] ; # 
  fhir:meta [
    ( fhir:profile [
fhir:v "http://hl7.org/ehrs/StructureDefinition/FMHeader"^^xsd:anyURI ;
fhir:link <http://hl7.org/ehrs/StructureDefinition/FMHeader>     ] )
  ] ; # 
  fhir:text [
fhir:status [ fhir:v "extensions" ] ;
fhir:div "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n    <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Manage and document the health care needed and delivered during an encounter/episode of care.</p>\n</div></span>\n\n    \n    <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Using data standards and technologies that support interoperability, encounter management promotes patient-centered/oriented care and enables real time, immediate point of service, point of care by facilitating efficient work flow and operations performance to ensure the integrity of (1) the health record, (2) public health, financial and administrative reporting, and (3) the healthcare delivery process.</p>\n<p>This support is necessary for care provision functionality that relies on providing user interaction and workflows. These interactions and workflows are configured according to clinical protocols and business rules. These protocols and rules are based on encounter specific values such as care setting, encounter type (inpatient, outpatient, home health, etc.), provider type, patient's EHR, health status, demographics, and the initial purpose of the encounter.</p>\n</div></span>\n    \n\n    \n\n    \n    <table id=\"statements\" class=\"grid dict\">\n        \n    </table>\n</div>"
  ] ; # 
  fhir:url [ fhir:v "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.7"^^xsd:anyURI] ; # 
  fhir:version [ fhir:v "0.16.0"] ; # 
  fhir:name [ fhir:v "AS_7_Support_Encounter_Episode_of_Care_Management"] ; # 
  fhir:title [ fhir:v "AS.7 Support Encounter/Episode of Care Management (Header)"] ; # 
  fhir:status [ fhir:v "active"] ; # 
  fhir:date [ fhir:v "2024-08-12T10:56:01+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 "Manage and document the health care needed and delivered during an encounter/episode of care."] ; # 
  fhir:purpose [ fhir:v "Using data standards and technologies that support interoperability, encounter management promotes patient-centered/oriented care and enables real time, immediate point of service, point of care by facilitating efficient work flow and operations performance to ensure the integrity of (1) the health record, (2) public health, financial and administrative reporting, and (3) the healthcare delivery process.\n\nThis support is necessary for care provision functionality that relies on providing user interaction and workflows. These interactions and workflows are configured according to clinical protocols and business rules. These protocols and rules are based on encounter specific values such as care setting, encounter type (inpatient, outpatient, home health, etc.), provider type, patient's EHR, health status, demographics, and the initial purpose of the encounter."] . #