Import and maintain
Provider updates, CSV and XLSX imports, FHIR Bundles and partner change proposals.
Technical implementation
A directory your systems can work with.
Connect service information to the applications that need it. Hark combines a shared provider model, standards-based interfaces and directory-level controls, so integration does not become another spreadsheet to maintain.
A shared provider model
Organisations, locations, services and practitioner roles, with review, provenance and audience controls.
Publish and connect
Branded directories, REST and FHIR reads, exports, change feeds and signed webhooks.
FHIR and APIs
Use a documented interface. Keep your own experience.
Build service discovery into referral software, contact centres and your own digital front door. REST responses expose directory information as JSON, with an OpenAPI contract for requests and responses.
FHIR R4, with a clear contract
The FHIR 4.0.1 server supports read and search for Organization, Location, HealthcareService, Practitioner, PractitionerRole and Endpoint resources. Its CapabilityStatement describes supported interactions and search parameters.
The FHIR server is read-only. Imports and authorised partner change proposals use separate workflows, so proposed changes can pass through the directory’s governance.
Keep downstream systems current
Partners can consume a change feed, receive signed webhooks or request exports. OAuth client credentials and directory grants define access; a grant can be narrowed by area, service category and record type.
Data and governance
Quality is part of the operating model.
Bring existing data into a structured graph of organisations, locations and services. Import validation and dry-run reports help teams review issues before committing a migration.
Make maintenance accountable
Provider editing, approvals, review reminders and curator work queues give records an owner. Data-quality reporting helps the team focus on gaps and information that needs attention.
Apply visibility across channels
Audience rules and partner scopes determine what a caller can receive across the API, FHIR and exports. Confidential locations and restricted practitioner information are handled in the shared publication layer.
Connected directories retain source information. Teams can trace where a record came from and direct corrections back to the responsible source.
Directory configuration
Shared foundations. Local control.
Each directory can define its identity, scope and ways of working while using the same underlying platform.
- Brand and access: custom domains, directory branding and role-based administration.
- Local context: service categories, geography, languages and country-specific reference data.
- Connected networks: bring participating directories into a wider view with source attribution and agreed sharing rules.
- Identity: staff authentication, MFA and SSO configuration, alongside scoped machine-to-machine access.
Implementation planning covers hosting, data residency, identity integration and operating responsibilities for your deployment.
Implementation pathway
Start with a useful slice. Prove the connections.
- Map the data. Agree source systems, identifiers, ownership, service categories and the information each audience may see.
- Validate a sample. Dry-run an import, review quality issues and confirm how records appear in search and API responses.
- Connect and test. Confirm resource mappings, partner grants, updates and error handling against your consuming systems.
- Prepare the team. Set review responsibilities, identity access, rollout scope and support arrangements before launch.