Developer API
Build on the Aimedis Family
Explore clinical integration patterns with scoped credentials, patient consent, and FHIR R4 resources through the partner program. For governed reference content, connect your AI through the separate Aimedis Wiki API guide.
Clinical Integration Patterns
to Integrate with Aimedis
Consent & Access API
Patient grants define scoped clinical access. Confirm the grant lifecycle, revocation timing, and audit guarantees in the partner service contract; recheck access on every protected request.
FHIR R4 Resource Patterns
The clinical examples use FHIR R4 resource patterns for vital signs, diagnoses, medications, and other record categories. Confirm the supported resources and operations with the service owner.
Cross-Platform Integration
Explore booking, patient-record, practice-calendar, intake, and professional-verification handoffs. The participating services define which flows are available in your deployment.
Specialist Module APIs
Explore integration areas for Aimedis Rehab, Aimedis Insur, Aimedis Decision Pro, and Aimedis Support. Each service has its own approved endpoint, authentication, consent, and data contract.
Security & Audit
Confirm encryption, secure PIN handling, access checks, and audit coverage with the service owner. A hash chain can make changes detectable; it does not establish immutable storage or universal audit coverage.
API at a Glance
Illustrative consent operations for clinical integration. These manage grant metadata; the partner service supplies the actual service origin, authentication requirements, and protected record-read contract.
/api/consent/generateCreate a scoped, PIN-protected grant — patient token/api/consent/redeemRedeem a patient PIN once for scoped access — practitioner token/api/consent/grantsList active grants — patient token/api/consent/grants/{consentId}Revoke a grant — confirm timing in the service contractComing Next — Not Live Today
Clinical self-service tooling is described as roadmap work. Confirm clinical access and delivery plans with the partner program; Wiki API access follows its separate documented process.
Match the integration to the data: clinical records require approved credentials and patient consent; Aimedis Wiki reference retrieval uses a separate contract for governed knowledge.
Start Building
Request the clinical partner contract or follow the Wiki API guide for reference retrieval.