Home / The OS / Government services
Finance, claiming and compliance teams

Services Australia and the Department of Health, built in

Government claiming and reporting run from work your team already recorded. Month-end stops being a marathon through portals, because every claim and report is built from one record.

ACWS Admin console in HealthOS listing Aged Care Web Services operations, from configuration and the PRODA connection test to care recipient search
Across care settings
Home care

Support at Home budgets, client contributions and claims through Aged Care Web Services, from the same record as the visits.

Residential aged care

Entry, departure, leave and supplement events and claims through ACWS, with Quality Indicators and 24/7 RN reporting lodged through GPMS.

Disability & NDIS

NDIS plan and participant management. Claiming through PRODA and PACE is in development.

Medicare & health funds

Medicare, DVA and private health insurer claiming through Eclipse and Medicare Online, with eligibility checked first.

What it does

Every government rail, native to the platform

Aged care & Support at Home
Production NOI in progress

ACWS: every event and claim in one workflow

HealthOS handles the full Aged Care Web Services lifecycle with Services Australia, from care recipient identity through to residential and Support at Home claiming. Claims are prepared from service records, submitted to Services Australia and reconciled against payment statements automatically. Conformance testing is complete, and the production notice of integration (NOI) is in progress.

  • Care recipient search and summary
  • Residential care entry, departure, leave and occupancy events
  • Support at Home budgets, contributions and claims
  • Claims, payment statements and reconciliation
  • Supplementary events: oxygen, enteral feeding and extra service
ACWS Sync screen in the intake module, showing the sync history of care recipients pulled from Services Australia and matched against existing persons
Department of Health
In conformance assessment

GPMS: mandatory reporting straight from the record

The Department of Health's mandatory aged care reports are lodged through its business-to-government (B2G) gateway in FHIR, the standard health-data format. The clinical data your staff already capture becomes the submission, so nothing is re-keyed into the GPMS portal. The GPMS B2G integration is in conformance assessment against the ADHA conformance scheme.

  • National Quality Indicators (NQIP), quarterly, per service
  • 24/7 Registered Nurse coverage, with monthly attendance and declarations
  • Provider, service, outlet and client reference data lookups
  • Care minutes and Quarterly Financial Report data prepared for lodgement
GPMS B2G Operations Console in HealthOS, showing each B2G authentication and registration operation as a runnable card
Identity
Production go-live in progress

HI Service, IHI and Medicare validation

Look up Individual Healthcare Identifiers (IHI) and validate provider identifiers (HPI-I and HPI-O) through the Healthcare Identifiers Service, authenticated with a NASH PKI certificate over a secure channel. Medicare numbers and DVA entitlements are verified in real time, directly from the client record. HI Service conformance has passed, and production go-live is in progress.

A person’s record with their IHI verified and active against the Healthcare Identifiers Service, and Medicare on file.
Medicare & health funds

Eclipse and Medicare Online claiming

Real-time Medicare, DVA and private health insurer claiming through Eclipse and Medicare Claiming Online (MCOL). Eligibility is checked before you bill, and remittance advices are retrieved and reconciled automatically.

  • Real-time eligibility checking
  • Automated claim submission
  • Reconciliation and reporting
  • Error handling and resubmission
Eclipse claim batches in HealthOS: a completed batch with its accepted and rejected claims, and a draft ready to submit.

From service record to reconciled payment

Every government submission is built from the Canonical Care Record. The data your staff already capture is the data that gets claimed and reported, with no re-keying along the way.

StepWhat happens
1. Deliver and recordA service is delivered and signed for. The event lands on the person's care record as structured data, with no separate claiming spreadsheet.
2. Build the claimHealthOS assembles the claim or report from the record, maps each field to the Services Australia or Department of Health specification, and validates it before anything is sent.
3. Submit via PRODAThe submission goes to the government gateway over an authenticated PRODA B2B channel. We manage and rotate the device-key credentials for you.
4. Reconcile automaticallyPayment statements and remittance advices are retrieved and matched back to the originating claim. Exceptions come to you for review, and the rest close themselves.
Several rails in progress

Conformance comes first

You can't process a government dollar until your software passes the government's own conformance testing. We have built and tested more than 30 Services Australia and Department of Health API clients against their published specifications. Here is where each rail stands.

RailStatus
HI ServiceConformance passed. Production go-live in progress.
Aged Care Web Services (Residential Care and Support at Home)Conformance testing complete. Production NOI in progress.
GPMS B2G (Department of Health)In conformance assessment against the ADHA conformance scheme.
My Health RecordIn development. Integration application submitted.
NDIS claiming (PRODA and PACE)In development, on the roadmap.
In development

My Health Record and NDIS claiming

Access to shared health summaries and discharge documents through My Health Record is in development, and the integration application has been submitted. Disability claiming through PRODA, the government's secure provider login, and PACE, the NDIS payments platform, is on the roadmap.

See Services Australia integration in action

We'll walk you through it on real data. Bring your questions.