Stream: implementers
Topic: Test/Observation
Pravina Munghate (Jul 04 2016 at 20:24):
Hi ,
I need inputs/suggestion on how I could save information addressing the requirement as described below using FHIR entities
Requirement is : There are few lab tests that needs to be explained and offered by a clinician , which could be accepted/rejected by a patient. If the test is taken by the patient then based on results , clinician might take some action - like a referral or further tests or could decide that no action is required. Tests can be recorded as Observation but how would I save the following elements in this workflow.
- The fact that Test was offered by a clinician and it was accepted/rejected by a patient along with a reason
- Resulting action(s) based on the test results and
- how should above information be linked to Test (Observation) entity
Thanks !
-Pravina
Grahame Grieve (Jul 04 2016 at 22:00):
- DiagnosticOrder + Task + Communication
- DiagnosticReport links to DiagnosticOrder
- Observation linked from DiagnosticReport
Lloyd McKenzie (Jul 05 2016 at 02:35):
As part of STU 3, DiagnosticOrder will be changed to DiagnosticRequest and will allow the capture of "proposals" and "plans" as well as orders. That, together with Task, will allow you to capture a recommendation as well as its acceptance/rejection.
Pravina Munghate (Jul 05 2016 at 20:38):
Thankyou ! Could I confirm that following needs to be captured as Task and not Communication ?
- Test offered/not offered by a clinician
- Acceptance / rejections by a patient
Lloyd McKenzie (Jul 05 2016 at 20:58):
Task is designed for managing workflow. Communication just maintains a record of what was shared.
Last updated: Apr 12 2022 at 19:14 UTC
