Encounter Clinical notes

[Levon Bedzhanyan]

Hello,

I am trying to figure out what scopes are to be used to ensure the patient can access the clinical notes for the past encounter. From my understanding, the flow should be the following:

GET /Encounter?:parameters -> GET /Encounter/:id -> GET /DocumentReference?:parameters -> GET /DocumentReference/:id -> GET /Binary/:id

Please confirm that this is the only way to get access to the clinical notes associated with the past encounters.

I was also wondering if Cerner has private APIs that could be utilized for this use case, but also for the appointment management workflows.

Thanks,

Levon

 

[Levon Bedzhanyan]

Hello,

I am following up on this ticket - can you please assist?

I am also wondering what would be the best way to pull the list of past appointments.

Thakns,

Levon

[Fenil Desani (Cerner)]

Hello Levon,

To get Encounter Clinical Notes, you can use DocumentReference resource with the Encounter search param

http://fhir.cerner.com/millennium/r4/foundation/documents/document-reference/#parameters

Once you have the content endpoint, you can use Binary resource to get the actual content of the document.

http://fhir.cerner.com/millennium/r4/foundation/other/binary/

Thanks,

Fenil

[Levon Bedzhanyan]

Fenil,

Thank you for the update on this ticket!

I've tested the flow to get the attachments, and do see that they come either in the pdf format or html.

Is it possible that there could be several attachments with various formats associated with one encounter? I'm trying to figure out all the possible cases.

And also - are the pdfs found more often, rather than the htmls? I'm specifically looking for the progress note (clinical note/soap note) submitted by the physician. Wondering if these always would come as HTMLs. 

If you also have a clinical note in mind that you might share so we can test it , that will be greatly appreciated.

Thanks,

Levon

[Fenil Desani (Cerner)]

A single encounter can have more than one clinical note and each can be in different format.

The consumer must populate the Accept header with either application/fhir+json or the format returned in the attachment.contentType of the referring resource. If the Accept header is application/fhir+json, a FHIR Binary resource is returned with the raw data populated in Binary.data. If the Accept header is anything else, the raw data will be returned instead of a FHIR Binary resource. For more information, see the HL7® FHIR® Binary documentation.

Note: in order to retrieve documents with the application/pdf content type, Cerner’s Clinical Reporting (XR) solution must be installed for the client site you are loading data from. For additional information about Cerner’s Clinical Reporting (XR) solution see Cerner’s Clinical Reporting (XR) Reference Pages.

[Levon Bedzhanyan]

Fenil,

Appreciate your prompt reply - thanks!