Halo Connect website screenshot

Halo Connect

Halo Connect is an Australian healthcare interoperability platform, founded in 2021 and headquartered in Brisbane, Queensland, that makes primary-care data integration simple by exposing on-premise practice management system (PMS) databases through a modern cloud API. Its Halo Link agent and Halo Cloud service let approved software integrators query systems such as Best Practice, Zedmed, and Dental4Windows using either SQL passthrough or a standards-based FHIR R4 (4.0.1) API built toward the AU Base 4.1.0 implementation guide, without maintaining a separate database agent per integration. Halo Connect built the first FHIR API for the Best Practice Premier medical-practice industry. The platform runs on Microsoft Azure hosted in Australia, and access is gated behind a Halo Cloud subscription using Azure API Management subscription keys and, for desktop applications, bearer JWT tokens issued from a token endpoint; there is no self-serve public API.

Halo Connect publishes 3 APIs on the APIs.io network: Halo Cloud API for Integrators, Halo Cloud API for Desktop Applications, and Halo Cloud FHIR API. Tagged areas include Healthcare, Australia, FHIR, HL7, and Interoperability.

The Halo Connect catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Halo Connect’s developer surface includes authentication, documentation, API reference, getting-started guide, engineering blog, changelog, sandbox, and 26 more developer resources.

58.3/100 developing ▬ flat Agent 75/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
3 APIs 1 MCP Servers
HealthcareAustraliaFHIRHL7InteroperabilityEHRPractice ManagementPrimary CareAU BaseHealth Data

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 58.3/100 · developing
Contract Quality 15.1 / 25
Developer Ergonomics 14.8 / 20
Commercial Clarity 7.4 / 20
Operational Transparency 7.5 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 75/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/halo-connect: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Halo Cloud API for Integrators

The Halo Cloud API for third-party software integrators to query on-premise practice management system databases over the cloud, covering site pairing, SQL passthrough (immediat...

Halo Cloud API for Desktop Applications

The Halo Cloud API for desktop applications, exposing a token endpoint plus SQL passthrough, FHIR R4 resource search, and registered-query operations under the /desktop path. Au...

Halo Cloud FHIR API

Halo Connect's FHIR API for accessing primary-care data from on-premise practice management systems, based on FHIR Release 4 (R4) version 4.0.1 and built toward the AU Base 4.1....

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Halo Connect Webhooks

Halo Cloud delivers HTTPS POST webhook notifications when an async or a registered query completes. The payload does NOT include the query result; the integrator retrieves resul...

ASYNCAPI

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Halo Connect Authentication

apiKey/http · 3 schemes

SECURITY

Halo Connect Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Halo Connect Vulnerability Disclosure

contact published

SECURITY

Halo Connect Trust Center

CyberCert SMB1001-2023 Level 3 (Gold), ISO 27001 (policies/procedures align to principles; not stated as certified)

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Halo Connect Agentic Access

29 operations · 14 acting

29 operations · 14 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Access & Security 6

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: halo-connect
url: https://raw.githubusercontent.com/api-evangelist/halo-connect/refs/heads/main/apis.yml
name: Halo Connect
kind: company
description: Halo Connect is an Australian healthcare interoperability platform, founded in 2021 and headquartered in Brisbane,
  Queensland, that makes primary-care data integration simple by exposing on-premise practice management system (PMS) databases
  through a modern cloud API. Its Halo Link agent and Halo Cloud service let approved software integrators query systems such
  as Best Practice, Zedmed, and Dental4Windows using either SQL passthrough or a standards-based FHIR R4 (4.0.1) API built
  toward the AU Base 4.1.0 implementation guide, without maintaining a separate database agent per integration. Halo Connect
  built the first FHIR API for the Best Practice Premier medical-practice industry. The platform runs on Microsoft Azure hosted
  in Australia, and access is gated behind a Halo Cloud subscription using Azure API Management subscription keys and, for
  desktop applications, bearer JWT tokens issued from a token endpoint; there is no self-serve public API.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Healthcare
- Australia
- FHIR
- HL7
- Interoperability
- EHR
- Practice Management
- Primary Care
- AU Base
- Health Data
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.19'
apis:
- aid: halo-connect:halo-cloud-integrator-api
  name: Halo Cloud API for Integrators
  description: The Halo Cloud API for third-party software integrators to query on-premise practice management system databases
    over the cloud, covering site pairing, SQL passthrough (immediate and async queries), FHIR R4 resource search, and registered
    (recurring) queries. Authenticated with an Azure API Management subscription key.
  humanURL: https://docs.haloconnect.io/halo-cloud/overview/
  baseURL: https://api.haloconnect.io
  tags:
  - FHIR
  - Healthcare
  - Interoperability
  - SQL
  properties:
  - type: OpenAPI
    url: openapi/halo-connect-integrator-openapi.json
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/overview/
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/integrator-openapi.html
- aid: halo-connect:halo-cloud-desktop-api
  name: Halo Cloud API for Desktop Applications
  description: The Halo Cloud API for desktop applications, exposing a token endpoint plus SQL passthrough, FHIR R4 resource
    search, and registered-query operations under the /desktop path. Authenticated with an Azure API Management subscription
    key, a bearer JWT, and a device identifier header.
  humanURL: https://docs.haloconnect.io/halo-cloud/overview/
  baseURL: https://api.haloconnect.io
  tags:
  - FHIR
  - Healthcare
  - Interoperability
  - SQL
  properties:
  - type: OpenAPI
    url: openapi/halo-connect-desktop-openapi.json
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/overview/
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/desktop-openapi.html
- aid: halo-connect:halo-cloud-fhir-api
  name: Halo Cloud FHIR API
  description: Halo Connect's FHIR API for accessing primary-care data from on-premise practice management systems, based
    on FHIR Release 4 (R4) version 4.0.1 and built toward the AU Base 4.1.0 implementation guide. Requests are site-scoped
    under https://api.haloconnect.io/integrator/sites/{haloGuid}/fhir/R4/{resourceType} and support search, read, and the
    Patient $summary operation. Supported resources (for example Patient, Practitioner, Appointment, DocumentReference) vary
    per PMS, and a live CapabilityStatement is served at {baseUrl}/metadata behind subscription authentication.
  humanURL: https://docs.haloconnect.io/halo-cloud/fhir-api/overview/
  baseURL: https://api.haloconnect.io
  tags:
  - FHIR
  - Healthcare
  - AU Base
  - Interoperability
  properties:
  - type: OpenAPI
    url: openapi/halo-connect-integrator-openapi.json
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/overview/
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/capabilities/
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/integrator-openapi.html
common:
- type: AgenticAccess
  url: agentic-access/halo-connect-agentic-access.yml
- type: DomainSecurity
  url: security/halo-connect-domain-security.yml
- type: Authentication
  url: authentication/halo-connect-authentication.yml
- type: Website
  url: https://haloconnect.io/
- type: DeveloperPortal
  url: https://docs.haloconnect.io/
- type: Documentation
  url: https://docs.haloconnect.io/
- type: APIReference
  url: https://docs.haloconnect.io/api-reference/integrator-openapi.html
- type: GettingStarted
  url: https://docs.haloconnect.io/halo-cloud/getting-started/
- type: StatusPage
  url: https://status.haloconnect.io/
- type: TrustCenter
  url: https://haloconnect.io/trust
- type: Blog
  url: https://haloconnect.io/blog
- type: ChangeLog
  url: changelog/halo-connect-changelog.yml
- type: Lifecycle
  url: lifecycle/halo-connect-lifecycle.yml
- type: Deprecation
  url: https://haloconnect.io/sla
- type: ErrorCatalog
  url: errors/halo-connect-error-codes.yml
- type: Conventions
  url: conventions/halo-connect-conventions.yml
- type: Sandbox
  url: sandbox/halo-connect-sandbox.yml
- type: Conformance
  url: conformance/halo-connect-conformance.yml
- type: Compliance
  url: https://haloconnect.io/trust
- type: AsyncAPI
  url: asyncapi/halo-connect-webhooks-asyncapi.yml
- type: Webhooks
  url: asyncapi/halo-connect-webhooks-asyncapi.yml
- type: VulnerabilityDisclosure
  url: security/halo-connect-vulnerability-disclosure.yml
- type: Security
  url: https://docs.haloconnect.io/security/
- type: MCPServer
  url: mcp/halo-connect-mcp.yml
- type: LLMsTxt
  url: llms/halo-connect-llms.txt
- type: DataModel
  url: data-model/halo-connect-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Overlay
  url: overlays/halo-connect-integrator-overlay.yaml
- type: Overlay
  url: overlays/halo-connect-desktop-overlay.yaml
- type: WellKnown
  url: well-known/halo-connect-well-known.yml
- type: TermsOfService
  url: https://haloconnect.io/terms-and-conditions
- type: PrivacyPolicy
  url: https://haloconnect.io/privacy-policy
- type: Support
  url: https://haloconnect.io/contact-us
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com