FHIR Chat · How to represent a (tumor)conference · implementers

Stream: implementers

Topic: How to represent a (tumor)conference


view this post on Zulip Patrick Werner (Mar 20 2018 at 14:32):

We are currently implementing a FHIR based tumor conference software. We are uncertain how to represent the actual conference (which includes the planned Date of the conference, Patient information, DiagReports, Documents, etc..). Currently in our consideration:

view this post on Zulip Patrick Werner (Mar 20 2018 at 14:33):

Appointment (which is more Workflow focused)
Encounter (which scope is more focused on the actual participation of the patient)

view this post on Zulip Lloyd McKenzie (Mar 20 2018 at 14:53):

@Brian Postlethwaite ?

view this post on Zulip Stefan Lang (Mar 20 2018 at 15:24):

Appointment seems like a good starting point to me.
- it offers time and context information
- it offers participant information
- supportingInformation allows to refer every information you might need for the tumor conference
- comment even allows for free text notes, in case your other question relates to that

view this post on Zulip Patrick Werner (Mar 20 2018 at 15:42):

Thanks for your comment, Appointment is also our favorite at the moment. We are just insecure because of the emphasis of the Workflow pattern in the scope description.
A tumorboard won't (directly) lead to encounters, nor will it have a AppointmentResponse following. Apart from that it fits quite well.
Yes the other question is related to this question ;-) but comment alone would be to unstructured to capture the notes of the different participants. Currently we are thinking about a extension on particpant to capture the individuals plain text notes.

view this post on Zulip Stefan Lang (Mar 20 2018 at 15:52):

Right with comment being probably too simple.
From my experience with tumor conferences, some person would document the decisions, while the individual participant's notes would have been less important.

I would also consider CarePlan representing the decision a tumor board makes in the context of a certain patient's tumor condition. So maybe it's CarePlan.note you're looking for?

view this post on Zulip Stefan Lang (Mar 20 2018 at 15:57):

Concerning scope:
"Examples include [...] a scheduled conference call between clinicians to discuss a case [...]".
Ok, many tumor conferences are in-person as of today, but I see the scope fitting perfectly.

view this post on Zulip Patrick Werner (Mar 20 2018 at 15:58):

CarePlan is also in our scope as the result of the conference. The notes are notes taken before the actual conference is conducted.

view this post on Zulip Stefan Lang (Mar 20 2018 at 15:59):

But wouldn't these notes be part of the diagnostic process, like a pathology report, some imaging, and clinical findings?

view this post on Zulip Patrick Werner (Mar 20 2018 at 16:00):

thanks for the comment and confirmation that Appointment is a considerable choice.

view this post on Zulip Patrick Werner (Mar 20 2018 at 16:02):

No these notes are thoughts of practitioners on the case when analyzing the available information during the preparation phase of the meeting, like a memory aid until the actual conference is scheduled. At this stage this won't be structured information/ practitioners are hard to motivate to structure their thoughts. We will be lucky to have structured data as a outcome at the end of the conference.

view this post on Zulip Stefan Lang (Mar 20 2018 at 16:03):

I know exactly what you mean ;)

view this post on Zulip Stefan Lang (Mar 20 2018 at 16:03):

How about ClinicalImpression.note then?

view this post on Zulip Stefan Lang (Mar 20 2018 at 16:04):

You could reference these via Appointment.supportingInformation

view this post on Zulip Patrick Werner (Mar 20 2018 at 16:08):

will have a look, thanks

view this post on Zulip Brian Postlethwaite (Mar 23 2018 at 00:59):

Sorry for my tardiness getting back to this one, all the advice here makes sense.


Last updated: Apr 12 2022 at 19:14 UTC