By Luke Benson. Last reviewed 13 September 2026.
Yes, if the platform speaks the standards your systems already speak. The most common objection to a new digital tool in care is “another silo”. Providers are right to be wary of point solutions that create one more island of data, disconnected from the clinical record, the care management system and the finance system.
Two standards answer the objection. HL7 is the long-established language of hospital system messaging. FHIR (Fast Healthcare Interoperability Resources) is the modern web-based standard for exchanging health data, now the default for new integration work in Australia and internationally. A service confirmation platform that speaks both can send a delivery record to almost any system that matters.
What should flow, and where:
- The check-in record (worker, participant, service, time, location) to the care management system, so it sits beside the care plan and the roster.
- The visit record to the clinical system, so the next clinician can see that the scheduled visit happened.
- The matched delivery record to finance, so invoice matching and claiming run off evidence rather than off the invoice alone.
For a Support at Home provider, the payoff is that the evidence section 10.5 of the program manual requires is not held in a separate tool that someone has to remember to check. It arrives in the systems where claims are prepared and reviewed.
For a provider evaluating tools, interoperability is the difference between an asset and a liability over a five-year horizon. Ask any vendor which standards they support and which systems are live today, not on a roadmap.
How DidYouGo fits. DidYouGo is built on FHIR and HL7. Live integrations today: InterSystems TrakCare and IRIS for Health for hospital and community health settings, and The Lookout Way for community care providers. Everything is also available through the API and as CSV export.

