A

AQORIO

Orchestration · Context · Governance · Execution

ConfidentialSynthetic data · adapters in mock modeAqorio is not a practice management system

01

Integration Hub

Every product below is reached through the identical IntegrationAdapter contract, so integrations are interchangeable and nothing in Aqorio's model is vendor-shaped.

Digitail

Practice management system

connectedmock mode

Source practice management system for this workflow. Emits the consultation-completed event.

Granted scopes

pms.encounter:readpms.clinical_note:writepms.appointment_request:writepms.task:write

Exposed capabilities

  • encounter.readread

    Read completed consultation + linked records

    requires: encounter reference

  • clinical_note.writewrite

    File a structured consultation note

    requires: encounter id, structured note

  • recheck.requestwrite

    Raise a recheck request on the practice diary

    requires: patient id, interval, reason

  • task.createwrite

    Create a clinician review task

    requires: patient id, task detail

Vetrics

Practice management system

connectedmock mode

Second practice system on the same adapter contract. Billing and dispensing exist only as external capabilities Aqorio calls.

Granted scopes

pms.encounter:readpms.charge_line:writepms.client:write

Exposed capabilities

  • encounter.readread

    Read completed appointment + linked notes

    requires: appointment reference

  • charge.line.createwrite

    Add a dispensed-medication charge line (external billing capability)

    requires: encounter id, product code, quantity

  • client.record.syncwrite

    Sync client contact + consent record

    requires: client id, contact fields

Provet Cloud

Practice management system

availablemock mode

Provet Cloud REST adapter built on OAuth 2.0 client_credentials. Governed vertical slice: resolve a patient, bind a consultation and attach exactly one preliminary clinical note after explicit human approval. Dry run until sandbox credentials exist.

Granted scopes

patients-clientsconsultationsclinical-notes

Exposed capabilities

  • patient.searchread

    Search patients by name

    requires: patient name fragment

  • patient.readread

    Read a patient record

    requires: resource id

  • client.readread

    Read the owning client record

    requires: resource id

  • consultation.searchread

    List consultations for a patient

    requires: resource id

  • consultation.readread

    Read an authoritative consultation

    requires: resource id

  • consultation.preliminary_note.createwrite

    Attach one preliminary clinical note (type 2)

    requires: consultation id, patient resource URL, reviewed note text

  • consultation.changed.observeread

    Consultation-changed webhook signal, then authoritative refetch

    requires: resource id

LAIKA

Clinical AI agent

availablemock mode

LAIKA API v1.01 adapter: system-level and user-level authentication with token refresh, patient read/create, medical-record create and 72-hour consultation sessions. Dry run until AITEM supplies a base URL and credentials.

Granted scopes

external-systemuserpatientsmedical-recordssessions

Exposed capabilities

  • systemLoginread

    External system login

    requires: externalSystemAccessToken

  • refreshSystemTokenread

    Refresh external system token

    requires: externalSystemAccessToken

  • userLoginread

    User login

    requires: externalSystemAccessToken

  • refreshUserTokenread

    Refresh user token

    requires: externalSystemAccessToken

  • listUsersread

    List users (admin)

    requires: externalSystemAccessToken

  • retrieveUserread

    Retrieve a user (admin)

    requires: externalSystemAccessToken

  • createUserwrite

    Create a user (admin)

    requires: externalSystemAccessToken

  • modifyUserwrite

    Modify a user

    requires: externalSystemAccessToken, userAccessToken

  • listPatientsread

    List patients

    requires: externalSystemAccessToken, userAccessToken

  • retrievePatientread

    Retrieve a patient

    requires: externalSystemAccessToken, userAccessToken

  • createPatientwrite

    Create a patient

    requires: externalSystemAccessToken, userAccessToken

  • modifyPatientwrite

    Modify a patient

    requires: externalSystemAccessToken, userAccessToken

  • createMedicalRecordwrite

    Create a medical record

    requires: externalSystemAccessToken, userAccessToken

  • createOrRetrieveSessionwrite

    Create or retrieve a consultation session

    requires: externalSystemAccessToken, userAccessToken

Heidi

Clinical AI agent

connectedmock mode

Clinical AI agent. Receives canonical context from Aqorio and returns structured output. No write permissions.

Granted scopes

agent.clinical_ai:invoke

Exposed capabilities

  • consult.reasonreason

    Reason over a consultation and return a structured clinical output

    requires: encounter, patient, clinical records

Client Communications

Client communications

connectedmock mode

Outbound client messaging. Consent is checked by Aqorio governance before any send is permitted.

Granted scopes

comms.message:send

Exposed capabilities

  • message.sendnotify

    Send a client message on their preferred channel

    requires: client contact, clinical-updates consent, message body

02

Registered agents

Services Aqorio may route work to.

  • Heidi — Consultation Reasoner

    Turns a completed consultation into a structured note, findings and recommendations.

    encounter.completed

  • Aqorio — Owner Summary Composer

    Renders clinical output into plain language for the owner, within consent limits.

    agent_output.available

  • Aqorio — Trend Watch

    Compares longitudinal values in context and raises internal review flags.

    context.assembled

03

Governance rules in force

  • · No external write or send executes before a human approval decision is recorded.
  • · Client messaging additionally requires an active clinical-update consent on the canonical client record.
  • · Adapters may only be called with capabilities inside the scopes granted to that integration.
  • · Every read, translation, routing decision, approval and write is appended to the execution audit log.