FHIR Chat · Attachments · implementers

Stream: implementers

Topic: Attachments

Rick Geimer (Sep 17 2016 at 12:25):

Starter for the 2016 Connectathon Attachments track

Rick Geimer (Jan 14 2017 at 15:04):

Thread starter for the Connectathon Attachments track.

Rick Geimer (Jan 14 2017 at 15:07):

http://wiki.hl7.org/index.php?title=201701_Attachments

Michele Mottini (Jan 14 2017 at 16:07):

Hi, I am here

Michele Mottini (Jan 14 2017 at 16:45):

Banner Health does not show up in my client - bug

Michele Mottini (Jan 14 2017 at 16:46):

I see a communication: pasted image

Michele Mottini (Jan 14 2017 at 16:52):

Actually - it is a bug in the HAPI server

Michele Mottini (Jan 14 2017 at 16:54):

pasted image

Oliver Krauss (Jan 14 2017 at 17:12):

Heya. Anyone already ready to play provider?
We have a request waiting for a Communication on http://fhirtest.uhn.ca/baseDstu3/CommunicationRequest/14541

Michele Mottini (Jan 14 2017 at 17:14):

It has no subject - is that OK ?

Michele Mottini (Jan 14 2017 at 17:14):

also: the identifier has no system

Rick Geimer (Jan 14 2017 at 17:16):

It should have a subject, so Oliver please add the following:

"subject": [
{
"reference": "Patient/good-health-patient-1"
}

Rick Geimer (Jan 14 2017 at 17:17):

The identifier should have a system too, but for connectathon purposes we can just use something like http://communicationrequest.example.org/

Rick Geimer (Jan 14 2017 at 17:18):

Hi Michele, I just did some testing of your application, and it is looking good.

Michele Mottini (Jan 14 2017 at 17:18):

OK, great

Reinhard Egelkraut (Jan 14 2017 at 17:19):

@Rick Geimer
ok, thanks for the Infos, we will adjust our requests accordingly

Rick Geimer (Jan 14 2017 at 17:20):

@Michele Mottini Once I get a few minutes of peace I will update my code to respond to your requests.

Michele Mottini (Jan 14 2017 at 17:21):

OK, sure

Michele Mottini (Jan 14 2017 at 17:22):

Are Christol or Chris around?

Rick Geimer (Jan 14 2017 at 17:22):

Yes, they are both here.

Oliver Krauss (Jan 14 2017 at 17:23):

Whoops. Sorry bout that. Also just noticed the payload was missing. New Request here: http://fhirtest.uhn.ca/baseDstu3/CommunicationRequest/14547

Chris Cioffi (Jan 14 2017 at 17:24):

Hey, @Michele Mottini , This is Chris

Michele Mottini (Jan 14 2017 at 17:24):

Hi Chris

Chris Cioffi (Jan 14 2017 at 17:25):

Christol is resetting her password, she will get in soon

Michele Mottini (Jan 14 2017 at 17:27):

OK, thanks

Michele Mottini (Jan 14 2017 at 17:27):

@Oliver Krauss : yes, I can see the request now:

Michele Mottini (Jan 14 2017 at 17:27):

pasted image

Michele Mottini (Jan 14 2017 at 17:45):

The PDF in the two communications seems to be invalid / corrupted

Reinhard Egelkraut (Jan 14 2017 at 18:36):

@Oliver Krauss and I just implemented the Provider as well. If anyone has a communicationRequest (in hope for a PDF as response) and is willing to test with us, we would be happy to try it. Just post your request id in this Chat.

Michele Mottini (Jan 14 2017 at 18:56):

I just sent a request: http://fhirtest.uhn.ca/baseDstu3/CommunicationRequest/14621/_history/1

Michele Mottini (Jan 14 2017 at 18:57):

(I also updated our client)

Michele Mottini (Jan 14 2017 at 18:58):

Note that the request is for Patient/14566

Oliver Krauss (Jan 14 2017 at 19:36):

@Michele Mottini you should just have gotten a response http://fhirtest.uhn.ca/baseDstu3/Communication/14624

Michele Mottini (Jan 14 2017 at 19:39):

Yes, I can see it:

Michele Mottini (Jan 14 2017 at 19:39):

pasted image

Michele Mottini (Jan 14 2017 at 19:39):

...are you in Europe?

Michele Mottini (Jan 14 2017 at 19:40):

I cannot open the PDF though

Oliver Krauss (Jan 14 2017 at 19:42):

We are from Europe but currently in the Connecthatthon Room at the Attachments table.
The PDF was Base64 Encoded, so it should work (does when I download it). What Character-Set are you using when decoding?

Michele Mottini (Jan 14 2017 at 19:45):

mhh...decoding to bytes...let me try locally

Michele Mottini (Jan 14 2017 at 19:47):

I tried decoding it http://www.motobit.com/util/base64-decoder-encoder.asp and I still get an invalid PDF

Michele Mottini (Jan 14 2017 at 19:48):

The first few decoded characters are 'JVBERi0xLjUNC' that do not look like a PDF header

Oliver Krauss (Jan 14 2017 at 20:06):

Found the error. HAPI already encodes itself, and I did it again. The PDF was double-encoded, since I also double decoded I didn't notice the error on my system. Here the response with a single encoding http://fhirtest.uhn.ca/baseDstu3/Communication/14662

Michele Mottini (Jan 14 2017 at 20:08):

pasted image

Michele Mottini (Jan 14 2017 at 20:08):

looks fine to me now!

John Moehrke (Jan 14 2017 at 20:09):

FYI: I understand the IHE mACM -- Mobile Alert Communication Management -- profile might be similar to the Attachment test scenario? See http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_mACM.pdf -- Yes, it is only DSTU2, but let me know if it is conceptually alighned. Would be good to align if the same usecase.

John Moehrke (Jan 14 2017 at 20:22):

So... although CommunicationRequest is the central resource for both... nothing else is related... that is my asssessment of mACM vs Attachments connectathon testing.

Michele Mottini (Jan 14 2017 at 20:26):

@John Moehrke : yes, the intent seems very different

John Moehrke (Jan 14 2017 at 20:30):

so, with attachment, was DocumentManifest looked at? I had CR submitted prior to DSTU2 to add the Attachment data to DocumentManifest with rational that seems very similar to the use-case described.

Reinhard Egelkraut (Jan 14 2017 at 20:34):

@John Moehrke concerning mACM, it looks like the use cases are very different indeed
the solicited attachement use cases look like "please give me a report for patient XY" with the response "here you have it"
and if I read it right in mACM the focus lies on pure alerting like "something important did (or did not although it should) happen for patient XY" with the response "thanks for the info"

Oliver Krauss (Jan 14 2017 at 20:40):

Looking through mACM the workflow looks similar, even if the use cases described are differen tfrom the track.

The Attachments use case does align with the Workflow Pattern B (http://build.fhir.org/workflow-ad-hoc.html#optionb) However neither the Clearinghouse nor the unsolicited use cases are supported by any workflow pattern.

Patrick Haren (Jan 14 2017 at 20:45):

http://wiki.hl7.org/index.php?title=201701_Clinical_Reasoning_Track

Oliver Krauss (Jan 14 2017 at 20:55):

A more general question on CommunicationRequest. How would one define in what format you want an answer to the requeset? I know there is medium. But I mean more in the sense of "application/xml application/json" but also in the sense of "CCD, CDA, or PDF" similar to how endpoint (http://build.fhir.org/endpoint.html) has a payloadType and mimeType

Michele Mottini (Jan 14 2017 at 21:00):

Write it in the message?

Oliver Krauss (Jan 14 2017 at 21:02):

Yes there is that. But I meant also machine-readable. Not sure if that will be needed very often in CommunicationRequests

Lisa Nelson (Jan 14 2017 at 23:26):

Here is an example for Janie Appleseed (Patient/300) where her PCP requested a current copy of her Personal Advance Care Plan (CommunicationRequest/9), and she returned it to her PCP (Communication/12 and Composition/28). There also is an example where Janie updated her PACP and pushed a copy to her PCP (unsolicited) (Communication/13 and Composition/29).

Michele Mottini (Jan 15 2017 at 00:55):

I can see those CommunicationRequest but not the Communication

Rick Geimer (Apr 11 2017 at 18:00):

April 2017 Attachments track

Rick Geimer (Apr 11 2017 at 18:02):

https://github.com/jamesagnew/hapi-fhir/releases

Rick Geimer (Apr 11 2017 at 18:24):

http://64.9.200.46/index.php?title=201701_Attachments

Anton Selin (Apr 11 2017 at 18:31):

What is a script to kick off fhir server from standard-distribution?

Anton Selin (Apr 11 2017 at 18:34):

Should REST end point running on my machine (something like localhost:8080) to receive messages?

Rick Geimer (Apr 11 2017 at 18:46):

Here is the HAPI FHIR server endpoint: http://fhirtest.uhn.ca/baseDstu3

Rick Geimer (Apr 11 2017 at 18:53):

To test the HAPI FHIR server, try the following (should retrieve a patient resource):

http://fhirtest.uhn.ca/baseDstu3/Patient/good-health-patient-1

Michael Ambrose (Apr 11 2017 at 18:54):

Yes, that works.

Rick Geimer (Apr 11 2017 at 19:00):

If you are having DNS issues hitting hl7.org/fhir, try http://build.fhir.org

Rick Geimer (Apr 11 2017 at 19:01):

To request an attachment, use http://build.fhir.org/communicationrequest.html

Rick Geimer (Apr 11 2017 at 19:01):

To respond to a request, use http://build.fhir.org/communication.html

Rick Geimer (Apr 11 2017 at 19:07):

Sample CommunicationRequest

http://fhirtest.uhn.ca/baseDstu3/CommunicationRequest/69031

Rick Geimer (Apr 11 2017 at 19:08):

Participants can respond to this request with a Communication resource containing a payload.

Michael Ambrose (Apr 11 2017 at 19:59):

http://fhirtest.uhn.ca/baseDstu3/CommunicationRequest/69102/_history/1

Anton Selin (Apr 11 2017 at 20:01):

http://fhirtest.uhn.ca/baseDstu3/Communication/69103/_history/1

Rick Geimer (Apr 11 2017 at 20:19):

Public FHIR servers:

http://64.9.200.46/index.php?title=Publicly_Available_FHIR_Servers_for_testing

Steve Ordahl (Apr 11 2017 at 20:56):

Here is the Provider FHIR Server https://mshlsfhir3apiapp.azurewebsites.net

Steve Ordahl (Apr 11 2017 at 21:20):

https://mshlsfhir3apiapp.azurewebsites.net/Organization/good-health

Rick Geimer (Apr 12 2017 at 14:13):

https://fhirtest.uhn.ca/baseDstu3/CommunicationRequest/69354

Rick Geimer (Apr 12 2017 at 14:14):

https://mshlsfhir3apiapp.azurewebsites.net/CommunicationRequest/69031

Michael Ambrose (Apr 12 2017 at 15:22):

Steve, here's what I created in your server:Provider: https://mshlsfhir3apiapp.azurewebsites.net/Organization/e51127ee-f8b8-49cc-9b2f-931f68092192
Payer/Requester: https://mshlsfhir3apiapp.azurewebsites.net/Organization/b4580a57-5578-461f-8d38-e12238bf71e2
CommunicationRequest: https://mshlsfhir3apiapp.azurewebsites.net/CommunicationRequest/0f06b691-a55f-46fc-bd02-810e59d52e9d
Resultant communication: https://mshlsfhir3apiapp.azurewebsites.net/Communication/3ef221b1-17d5-4604-a942-de98681b8103

Michael Ambrose (Apr 12 2017 at 16:13):

Rick, here are the links to the Org->CommunicationRequest->Communication on your server:

My payer: http://fhirtest.uhn.ca/baseDstu3/Organization/69121

Provider I'm using: http://fhirtest.uhn.ca/baseDstu3/Organization/good-health

My communication request: http://fhirtest.uhn.ca/baseDstu3/CommunicationRequest/69126
(externalized payer, provider)

Response communication: http://fhirtest.uhn.ca/baseDstu3/Communication/69364

Last updated: Apr 12 2022 at 19:14 UTC