Stream: Post-Acute Care
Topic: scene 1 steps
Edward Castagna (Jan 15 2021 at 15:47):
Chirag, Matt,
Here is a revised sequence of events for Scene 1. We have already cleared the eLTSS CC FHIR Server in preparation for the start of Scene1
1-15-2021 Scene 1 Testing Recording 10:30am EST
1. Here is the sequence we envision for the Connectathon testing. Please confirm this is also your understanding/expectation.
2. Scene 1, Patient receiving LTSS while at home:
3. Altarum Clears Data from eLTSS CC FHIR Server
4. FEI uploads eLTSS bundle to eLTSS CC FHIR Server. FEI lets Altarum know the Bundle id (Bundle resource with contained eLTSS resources)
5. Altarum scripts copying the eLTSS contained resources from the bundle, converting them to individual eLTSS FHIR resources, then loading them to the eLTSS CC FHIR Server.
6. Altarum displays the Bundle resource on the eLTSS CC FHIR Server GUI.
7. Altarum runs a $everything on the eLTSS CC FHIR Server GUI showing that the contained resources were extracted from the bundle and loaded as individual eLTSS FHIR resources and data for the FEI Patient: Betsy Smith Johnson (with unique patient ID: “client…19”), on the eLTSS CC FHIR server.
8. There will be no attempt to deliver the FEI eLTSS FHIR resources and data for patient ID: “client…19” to the PCS Health Data Manager (HDM).
9. FEI - Done
10. Altarum Clears Data from eLTSS-CC Server
11. Altarum loads full Betsy Smith Johnson (Becky bundle) to eLTSS CC FHIR Server
12. Altarum will use their FHIR VUHR/Broker tool to broker the complete set of test data from the eLTSS CC FHIR Server to the PCS HDM FHIR Server. (patientBSJ1)
13. Altarum will display the set of eLTSS resources that were transmitted to the PCS HDM via the FHIR VUHR/Broker tool.
14. PCS will also display the eLTSS FHIR resources and data for patient: Betsy Smith Johnson on the HDM using their client/tool.
15. Altarum – Done.
16. MaxMD will upload an Advanced Directive (AD) to the eLTSS CC FHIR server (DocumentReference FHIR resource)
17. If necessary Altarum may show that the “DocumentReference” Resource was loaded to the eLTSS CC FHIR Server using the server GUI. (Requires a restart on the eLTSS CC FHIR Server – 5 minutes - to get the new counters in place in the GUI)
18. MaxMD will use their CDA Viewer application that will be pointed at the eLTSS CC FHIR Server DocumentReference resource to display the contents of the AD.
19. There will be no attempt to deliver the MaxMD AD to the PCS HDM.
20. MaxMD – Done.
John Moehrke (Jan 15 2021 at 16:30):
can we record here the URLs to the resources created during the scenario? (not necessarly browser renderable, the raw FHIR REST get would be good)
Forrest White (Jan 15 2021 at 16:37):
John, here is the $everything for Patient on the eLTSS CC FHIR Server: https://fhirconnect.altarum.org/hapi-fhir-jpaserver-eltss-CC/fhir/Patient/patientBSJ1/$everything
John Moehrke (Jan 15 2021 at 16:40):
I don't find a documentReference -- the scene one advanced directives thing...
Edward Castagna (Jan 15 2021 at 16:45):
we may be returning multiple pages within a $everything. so follow the next page link if you don't find a resource on the first page.
also https://fhirconnect.altarum.org/hapi-fhir-jpaserver-eltss-CC/fhir/DocumentReference and https://fhirconnect.altarum.org/hapi-fhir-jpaserver-eltss-CC/fhir/Binary would show the DocumentReference and Binary Resource instances added during the connect-a-thon.
John Moehrke (Jan 15 2021 at 16:48):
the DocumentReference.subject is set properly... so logically it should come along. But, yes they could implement $everything as a subset. but would be good to figure out why it isn't showing up.
John Moehrke (Jan 15 2021 at 16:49):
the Binary would not have a subject. One finds that by way of the DocumentReference. The whole purpose of DocumentReference is to provide metadata for Binary things
Edward Castagna (Jan 15 2021 at 16:50):
image.png
did that work showing that there was an additional Organization and Device delivered...
Edward Castagna (Jan 15 2021 at 16:56):
Would you know how to do the troubleshooting on the HAPI-FHIR Server configuration to figure out why it's not including it and where it might be good to ask for a modification request?
John Moehrke (Jan 15 2021 at 16:57):
organization would not show up on $everything. $everything is patient specific
John Moehrke (Jan 15 2021 at 16:57):
device could if the .subject is set right
John Moehrke (Jan 15 2021 at 16:59):
but, that gets to the point that the $everything might be just doing a subset of resources
John Moehrke (Jan 15 2021 at 16:59):
I don't know HAPI on that level
John Moehrke (Jan 15 2021 at 16:59):
it is also possible that your invocation of $everything has asked for a subset https://www.hl7.org/fhir/operation-patient-everything.html
Edward Castagna (Jan 15 2021 at 17:08):
I apologize. I found DocumentReference, Device, Organization on page2 of the Severything....
i think we're limiting to 20 resources or somesuch default on hapi
John Moehrke (Jan 15 2021 at 17:10):
oops.. yup, pages. I missed it too
Edward Castagna (Jan 15 2021 at 17:11):
sorry i missed it the first time... good day.
John Moehrke (Jan 15 2021 at 17:12):
and there is Device and Organizatino
John Moehrke (Jan 15 2021 at 17:12):
and a bunch of other stuff.
Edward Castagna (Jan 15 2021 at 17:24):
another hapi-fhir exposed url is the history on the fhir server where you can watch for recent updates to the server. for the purpose of finding what's happened on the server during a period of time... you can try https://fhirconnect.altarum.org/hapi-fhir-jpaserver-eltss-CC/history-server
multiple pages there also to get to the beginning of the day. we reset the server before putting in the patientBSJ1 transaction and getting the Advanced Directive from MaxMD
Last updated: Apr 12 2022 at 19:14 UTC
