-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
US Da Vinci CDex (FHIR)
-
current
-
Payer/Provider Information Exchange
-
Background
-
Unable to transition in Jira - see comments below
1) Add guidance for payer to document how they may provide some work queue tagging that Provider may use in their workflow to process request:
"For asynchronous requests using Task, it may be beneficial for Payers and EHRs to pre-coordinate and agree upon a set of "request-tags" to communicate the general type of request being made. The EHR can use these Payer supplied tags to aid in filtering and sorting Tasks. For example, assuming the EHR has work queues based on request criteria, tags could be used by the EHR to place a Task in the appropriate work queue
The way to tag a resource FHIR is to use Task.meta.tag ...
2) Provide An example starter set of tags : ~/Davinci-CDEX/output/ValueSet-cdex-work-queue.html
3) update CDEX Task Profile in include an optional meta.tag element slice:
4) and provide an example using a tag on Task
Background on meta.tag: ( not part of disposition )
Tags are used to relate resources to process and workflow. Applications are not required to consider the tags when interpreting the meaning of a resource.
On the RESTful API: On receiving a write operation, the server SHOULD preserve the labels unless applicable business rules dictate otherwiseExample:
Unable to transition in Jira - see comments below 1) Add guidance for payer to document how they may provide some work queue tagging that Provider may use in their workflow to process request: "For asynchronous requests using Task, it may be beneficial for Payers and EHRs to pre-coordinate and agree upon a set of "request-tags" to communicate the general type of request being made. The EHR can use these Payer supplied tags to aid in filtering and sorting Tasks. For example, assuming the EHR has work queues based on request criteria, tags could be used by the EHR to place a Task in the appropriate work queue The way to tag a resource FHIR is to use Task.meta.tag ... 2) Provide An example starter set of tags : ~/Davinci-CDEX/output/ValueSet-cdex-work-queue.html 3) update CDEX Task Profile in include an optional meta.tag element slice: 4) and provide an example using a tag on Task Background on meta.tag: ( not part of disposition ) Tags are used to relate resources to process and workflow. Applications are not required to consider the tags when interpreting the meaning of a resource. On the RESTful API: On receiving a write operation , the server SHOULD preserve the labels unless applicable business rules dictate otherwise Example:
(split out from multipart comment in FHIR-30870)
6) (duplicate of FHIR-30889 which due to a Jira bug is unreachable) Localizing non-structured data elements by SNOMED, ICD-10 or historical data will be very challenging due to multiple concepts within text blocks or dictated text under catch all identifiers and therefore flow to clinicians' workflow in-baskets.
7) Clinicians are concerned re increases in volume/frequency/complexity of requests from multiple/recurrent payers overflowing their workflow in-basket impacting patient care due to increased face to screen time especially if it cannot be accurately/automatically delegated to EHR/support staff.port staff.
- is duplicated by
-
-
- Duplicate
-
- relates to
-
-
- Published
-