Stream: implementers
Topic: Appointment visit motive
Thomas Bentkowski (Feb 20 2017 at 09:07):
.
Thomas Bentkowski (Feb 20 2017 at 09:12):
Hello,
I'm implementing FHIR at the moment and I'm having trouble dealing with appointment reasons.
I know I can use the value set available here : https://www.hl7.org/fhir/valueset-encounter-reason.html
or implement my own value set for it but it's still problematic because reasons are a resource in my app and practitioners can add, modify and delete them. Reasons also have various fields such as a color, ...
A value set won't be enough for my app.
A "reason" in my app is a visit motive or an appointment motive (visit and appointment are the same thing here). Sure, my visit motive is linked to my appointment but it is also a standalone resource in my app because you can CRUD it. A value set doesn't allow me to do all these actions on my visit motives that is why I can't use one and why I'm asking to create a "new resourceType". Here is the schema of my "visitMotive" a.k.a reason : pastebin.com/nECvfxqh
I've started a post on StackOverflow for this matter and already talked with @Lloyd McKenzie about it. I've discovered this chat just after, sorry for reposting here, I think it could be useful to others too. Here is the link to the question : https://stackoverflow.com/questions/42108964/fhir-appointment-reasons-as-a-resource/42115655?noredirect=1#comment71611388_42115655
Do you have any hints / ideas on how could I implement such thing ?
Cheers,
Thomas
Lloyd McKenzie (Feb 20 2017 at 09:20):
Some further background - the notion of "reason" here is more like a definition for a type of service to be provided and has a name, expected duration, type of specialty, etc. @Brian Postlethwaite, any thoughts?
Marc Robberecht (Mar 27 2017 at 09:02):
Hi @Brian Postlethwaite, can you advise if a new resource could be envisioned to answer Thomas's question. Being involved in the same project, we would need to decide to create a new resource aligned with a future change or keep it project specific... Or shall we make a GForge tracker for this request?
Marc Robberecht (Mar 27 2017 at 09:02):
Thx,
Marc
Last updated: Apr 12 2022 at 19:14 UTC
