Stream: questionnaire
Topic: Challenge
Grahame Grieve (Apr 06 2018 at 19:59):
There's a work flow that keeps coming up for me with different clients and implementers:
When the client submits some change/transaction/complicated request to the server, the server would like to ask the client arbitrary questions about the submission before processing it. We have a language for asking arbitrary questions... a questionnnaire. So the API would look something like this:
- client makes a request
- server responds with an async redirect, and a HATEOS link to a questionnaire for the client to present to the user.
- client pre-populates the questionnaire per SDC if it wants
- client presents the questionnaire to the user
- once the user has completed the questionnaire, the client submits it to the async task location, and the server either
- returns an error from processing the questionnaire, and the cycle restarts
- completes the task
- redirects to the task location while processing the task
Grahame Grieve (Apr 06 2018 at 20:03):
is anyone interested in this?
Alex Goel (Apr 10 2018 at 12:37):
We're interested. It makes sense if you have a jurisdictional authority that needs to host a form for a local hospital to fill out. Then that local hospital can load the link to the questionnaire if there are capability issues at the local site in getting a questionnaire running and SDC compliant. Places the burden on the Form Manager
Difficulty is how to prepopulate a form hosted outside the hospital. Does that require patient data sent to the Form manager?
Grahame Grieve (Apr 10 2018 at 21:56):
the client pre-populates the form outside the hospital
Eric Haas (Apr 11 2018 at 02:54):
Scheduling use case and @Cooper Thompson might be on board
Brian Postlethwaite (Apr 11 2018 at 05:23):
I'm interested.
Last updated: Apr 12 2022 at 19:14 UTC
