Stream: implementers
Topic: Communication Resource
Ville Lindholm (May 09 2017 at 18:31):
Hi guys! I just wanted to check that I have understood CommunicationRequest and Communication correctly. I want to send a simple text message from a decision support system via a healthcare provider to a user. Have I understood correctly that the CDS would issue a CommunicationRequest, the healthcare provider shows its payload and then (potentially) saves the payload in its archives as a Communication?
Lloyd McKenzie (May 09 2017 at 18:42):
That sounds right. The CDS system creates a "recommendation" CommunicationRequest asking for information to be seen to the user. When the Practitioner acts on the request, they create a record of that action as a COmmunication.
Ville Lindholm (May 09 2017 at 18:50):
That's what I thought. Thanks!
Jim Kane (May 22 2017 at 08:39):
Hi there
I'm currently trying to create a fhir communication in .NET using the spark fhir libraries and persisting against an existing user on the furore fhir server.
When I try to create the Communication resource (making sure there are the required fields in place) it refuses to persist. The exception tells me that data at the root level is invalid. I serialized out the object, and it is valid JSON(but doesn't upload using ARC/Postman.
Anyone faced this problem before? I can post my code if necessary
Grahame Grieve (May 22 2017 at 09:28):
are you posting to the wrong server version?
Jim Kane (May 22 2017 at 10:29):
@Grahame Grieve
I'm posting using the Hl7.Fhir.DSTU2.core (Version 0.92.1.0) to the http://spark.furore.com/fhir/Communication endpoint
Travis Stenerson (Aug 21 2017 at 18:53):
Quick question on Communication vs CommunicationRequest.
We would like to persist a record of having informed a CDS user something like "Testing for X is unnecessary". The user has not ordered testing for X, but we need to communicate it anyways. This user would have received this message while interacting with the CDS system (so the communication is pretty much complete), so it feels redundant to put this in a CommunicationRequest. What is the best way to accomplish this in FHIR? Communication or CommunicationRequest?
Thanks
Eric Haas (Aug 21 2017 at 19:07):
Communication. payload is "Testing for X is unnecessary"
Yogesh Mehra (Feb 15 2018 at 21:23):
Thinking of a scenario on an ongoing text messaging (chat) between a practitioner and patient -
Should each of the message going to-and-fro be modeled as a Communication object or the end to end conversation on a particular topic be modeled as a communication object. Both the options tie into an Encounter but in the former case there has to be a collection of Communication objects packaged into a container (Bundle/Composition/List/Other); In the latter, the Communication object has to be a container of multiple messages.
Would love to know the thoughts from the community on this scenario and the option that fits more into the overall FHIR model.
Joe Jordan (Mar 02 2021 at 18:27):
Interesting question, @Yogesh Mehra . I'm working on an implementation of the Communication resource and wondering the very same thing. Also considering the possibility of using the Communication resource as a mechanism for practitioners to create notes for themselves. They would be considered communications to themselves, which seems like a viable approach, but would be open to additional input.
Lloyd McKenzie (Mar 02 2021 at 19:14):
Communication nominally reflects information that was shared from one source to one or more participants. So it innately requires a single 'sender'. If you're representing a 'conversation' where the primary function was delivery of information from one party to another, then a single Communication is fine - even if there's a bit of back and forth in terms of questions, clarifications, etc. On the other hand if you want to communicate exactly what's being shared from one to another in sequence, then individual Communication instances might be better.
Last updated: Apr 12 2022 at 19:14 UTC
