Publish Box goes here

• Narrative Content
• XML
• JSON
• TTL

: AS.5 Manage Clinical Workflow Tasking (Header) - TTL Representation

Active as of 2024-11-23

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.5"] ; # 
  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>Create, schedule, update and manage tasks with appropriate timeliness.</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>Since an electronic health record will replace the paper chart or other paper-based system, tasks that were based on the paper artifact must be effectively managed in the electronic environment. Functions must exist in the EHR-S that support electronically any workflow that previously depended on the existence of a physical artifact (such as the paper chart, a phone message slip) in a paper based system. Tasks differ from other more generic communication among participants in the care process because they are a call to action and target completion of a specific workflow in the context of a patient's health record (including a specific component of the record). Tasks also require disposition (final resolution). The initiator may optionally require a response.</p>\n<p>For example, in a paper based system, physically placing charts in piles for review creates a physical queue of tasks related to those charts. This queue of tasks (for example, a set of patient phone calls to be returned) must be supported electronically so that the list (of patients to be called) is visible to the appropriate user or role for disposition. The state transition (e.g., created, performed and resolved) may be managed by the user explicitly or automatically based on rules. For example, if a user has a task to signoff on a test result, that task should automatically be marked complete by the EHR when the test result linked to the task is signed in the system. Patients will become more involved in the care process by receiving tasks related to their care.\nExample:\nExamples of patient related tasks include acknowledgement of receipt of a test result forwarded from the provider, or a request to schedule an appointment for a pap smear (based on age and frequency criteria) generated automatically by the EHR-S on behalf of the provider.</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.5"^^xsd:anyURI] ; # 
  fhir:version [ fhir:v "2.1.0"] ; # 
  fhir:name [ fhir:v "AS_5_Manage_Clinical_Workflow_Tasking"] ; # 
  fhir:title [ fhir:v "AS.5 Manage Clinical Workflow Tasking (Header)"] ; # 
  fhir:status [ fhir:v "active"] ; # 
  fhir:date [ fhir:v "2024-11-23T08:20:40+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 "Create, schedule, update and manage tasks with appropriate timeliness."] ; # 
  fhir:purpose [ fhir:v "Since an electronic health record will replace the paper chart or other paper-based system, tasks that were based on the paper artifact must be effectively managed in the electronic environment. Functions must exist in the EHR-S that support electronically any workflow that previously depended on the existence of a physical artifact (such as the paper chart, a phone message slip) in a paper based system. Tasks differ from other more generic communication among participants in the care process because they are a call to action and target completion of a specific workflow in the context of a patient's health record (including a specific component of the record). Tasks also require disposition (final resolution). The initiator may optionally require a response. \n\nFor example, in a paper based system, physically placing charts in piles for review creates a physical queue of tasks related to those charts. This queue of tasks (for example, a set of patient phone calls to be returned) must be supported electronically so that the list (of patients to be called) is visible to the appropriate user or role for disposition. The state transition (e.g., created, performed and resolved) may be managed by the user explicitly or automatically based on rules. For example, if a user has a task to signoff on a test result, that task should automatically be marked complete by the EHR when the test result linked to the task is signed in the system. Patients will become more involved in the care process by receiving tasks related to their care.\nExample:\nExamples of patient related tasks include acknowledgement of receipt of a test result forwarded from the provider, or a request to schedule an appointment for a pap smear (based on age and frequency criteria) generated automatically by the EHR-S on behalf of the provider."] . #