Communications
Approved SMS, email, WhatsApp and contact-centre pathways with consent, delivery and exception context.
Integration architecture
Connect through governed interfaces—not invisible point-to-point links.
AFIYORA's planned integration control plane is designed to make every connection, mapping, message, acknowledgement, retry and exception visible to authorised operators.
PATIENTCLINICPARTNER
AFIYORAINTEGRATION CONTROL
FHIRHL7DICOMAPI
Visible boundariesNative, partner and market scope separated
Versioned contractsMappings and profiles controlled
Operational recoveryRetry, quarantine and reconciliation
Accountable ownershipHuman review for consequential exceptions
PLANNED CONTROL PLANE
An interface is an operating responsibility.
Each connection needs a catalogue entry, owner, credentials, mapping version, message state, acknowledgement, retry policy, quarantine path and reconciliation evidence. AFIYORA should own this operational visibility even when a partner supplies the external service.
See implementation methodConnection and credential registryIdempotent retry and controlled replayMessage health and service-level monitoringMinimum necessary data and scoped access
Integration categories
Build the workflow. Integrate qualified specialist services.
The directory below communicates product direction only. A category is not evidence of a live connection, certification or country availability.
Payments & finance
Gateway, payment-link, settlement and accounting connections while AFIYORA retains workflow and reconciliation state.
Laboratory & diagnostics
Versioned order, result and acknowledgement interfaces with safe patient/order matching and exception worklists.
Imaging & PACS
Planned DICOM/DICOMweb metadata and secure viewer links rather than recreating a full imaging archive.
HIE & payer ecosystems
Country- and programme-specific adapters for authorised health exchange, eligibility, claims and remittance.
Identity & enterprise
Planned identity provider, SSO, provisioning and governed data-export pathways for enterprise customers.
Standards strategy
Use the right exchange model for each job.
Standards improve consistency, but every implementation still requires profile, security, identity, terminology and conformance decisions.
FHIR
Planned profile-specific APIs and HIE adapters. FHIR readiness is not certification or connection.
RoadmapHL7 v2
Planned order, result and facility messages with acknowledgements and reconciliation.
RoadmapDICOM / DICOMweb
Planned imaging metadata, query and viewer pathways through qualified infrastructure.
RoadmapREST APIs & webhooks
Planned scoped credentials, signing, idempotency, versioning and a developer sandbox.
RoadmapInterface lifecycle
Design for failure, recovery and change.
A successful first message is not an integration operating model.
01Define contract02Map & validate03Test exceptions04Release safely05Monitor health06Reconcile outcomes
PRODUCT CLARITYNo integration claim without verified evidence.
AFIYORA will identify each connection as available, planned, optional or requiring validation by market and edition. Standards logos or architectural readiness will never be presented as proof of acceptance by a regulator, payer or provider.
Ready for a clearer view?
Bring the interface into the operating model.
Share the external system, workflow, message direction, market and service-level expectation. We will separate platform work from partner and programme dependencies.