Ultimately this is just an orchestration tool for publishing HL7v2 messages. You have to write your own pathways and segments, or push preconfigured HL7v2 messages. Take a look at the dashboard, you'll see what I mean[1].
Fairly sure they built this to test their HL7v2 store[2]. Also presuming it hasn't been very active given that Google surprisingly shut down their Healthcare division (and probably restarted it somewhere)[3].
Very interesting! I have been working with medical information standards for a while now. Recently, I took an interest in DICOM and ways to modernize it. For example by introducing streaming, caching, moving metadata to a FHIR ImagingStudy resource.
To me, specifically streaming and caching strategies to move the load of (often hopelessly legacy) hospital infrastructure are an interesting challenge.
Fairly sure they built this to test their HL7v2 store[2]. Also presuming it hasn't been very active given that Google surprisingly shut down their Healthcare division (and probably restarted it somewhere)[3].
[1] https://github.com/google/simhospital/blob/master/docs/dashb... [2] https://cloud.google.com/healthcare-api/docs/concepts/hl7v2#... [3] https://www.businessinsider.com/google-health-shutting-down-...