Open joostholslag opened 2 months ago
I think this section was removed from the spec..... The ultimate goal is to make healthcare-processes a little more efficient. For the process the creating, updating and accepting a Task, the filler/recipient of the Task should automate that as much as possible (otherwise, the requesting/initiating practitioner (and patient) has to wait and/or re-initiate after a rejection). In https://santeonnl.github.io/shared-care-planning/overview.html#creating-and-responding-to-a-task a version with human verification (to accept a Task), in stead of automatisch Task-acceptance was introduced. Not sure if I've answered your question concerning data transformation and human verification.....
title appears to be a goal while reading https://github.com/SanteonNL/shared-care-planning/blob/main/input/pagecontent/introduction.md
How would this be made safe? Since data transformation (based on mappings) is a process based on assumptions. This brings risks for individual patients if different parties have different assumptions. Manual verification by both sender and receiver is common to mitigate this. Can we make it safe to automate this?