Integrate where your users already work.
The 6 places a cited chronology changes the product it sits inside.
Case management
Create cases from intake and keep processing state in sync, so the reviewer never leaves the queue.
Medical record retrieval
Add a structured review service after document collection, delivered inside the same portal.
Claims administration
Surface a source-linked medical timeline inside the claims workflow, next to the reserve.
IME and QME platforms
Populate draft report workflows for authorized evaluators from the assembled, cited record.
Review vendors
Push outputs into existing reviewer queues and stop re-keying facts between systems.
Legal-tech applications
Build case-specific search, chronology and report experiences on the evidence graph.
Structured outputs, not another manual export step.
Ingest, process, retrieve. Status and structured outputs populate your own UI; nobody downloads a PDF and re-types it.
Illustrative flow. Endpoint paths, authentication and schemas come from the technical documentation after approval, not from this page.
What the API covers.
Each capability with where it stands today. "Confirm on the call" means it exists in the product and the exact contract for your integration is settled in discovery.
| Capability | What it does | Status |
|---|---|---|
| Case creation | Create cases over REST with the record files, focus fields and report template, then list and read them by case | Available |
| File ingestion | Multipart upload on case creation, or direct-to-storage upload for large sets. PDF, scanned images and DICOM; no zip archives. Medical records OCR → | Available |
| Processing status | Poll case status and per-case progress. No outbound webhooks today; push notifications are a roadmap item | Polling today |
| Structured record data | Per case: dated record summaries, timeline grouped by date, providers, facilities, missing records, duplicates and exclusions. Chronology → | Available |
| Source citations | Record summaries carry page ranges; Q&A answers carry page-level citations with the source file. Verifiable citations → | Available |
| Chronology and report outputs | Structured content or branded exports. Export controls → | Available |
| Authentication | Bearer tokens issued per account today; how credentials are scoped to your tenancy is settled in the agreement | Confirm on the call |
| Tenant isolation | Partner and client segregation; architecture review on request | Confirm on the call |
| Rate limits and quotas | Agreed for your volume in discovery | Confirm on the call |
| Environments | Synthetic-case testing before production; sandbox shape agreed per integration | Confirm on the call |
A practical path from proof of concept to production.
6 steps, in the order they happen. Regulated data does not move until step 3 is signed.
- Describe the requirementCase volume, average pages, and the outputs your product needs.
- Technical fit callAuthentication, tenancy, file transfer, status polling, retention. Your engineers and ours.
- Agreement and permissionsThe right contract for the data involved, BAA included where PHI is in scope.
- Test with synthetic casesNon-PHI sample cases in the approved environment. No production data yet.
- Validate the integrationData mapping, citation integrity, error behaviour, retries and the reviewer handoff.
- ProductionContracted scope, deployment, observation, iteration.
Deploy for your architecture and compliance needs.
Data residency, network access and processing model differ per option; each is documented in its agreement.
Managed platform and API
Hosted by Medrecords AI, integrated over the API. Fastest to a proof of concept.
Your cloud tenancy
A flat annual license with the platform in your own AWS or Azure account and model inference billed there.
Your own network
The whole stack inside your infrastructure, air-gap available, for the contracts that require it.
The questions your security and engineering reviewers will ask.
Bring them to the technical call; where the answer is "it depends on your integration" we say so instead of guessing.
| Topic | Where the answer lives |
|---|---|
| PHI, BAA and permitted uses | HIPAA and BAA · DPA |
| Encryption and credential handling | Trust Center |
| Tenancy, logs and auditability | Architecture review on the technical call |
| Uptime and support commitments | Set out in the agreement; no blanket SLA is published here |
| Error handling, idempotency, concurrency | Technical documentation after approval |
| Versioning and deprecation | Technical documentation after approval |
| Webhooks | None today; status is polled. Ask on the call if your product needs push |
| Data retention and deletion | DPA and the agreement |
| Model training terms | Customer records never train a model; contractual under the BAA |
| Source provenance | Verifiable citations · Chronology |
Pricing for your use case and volume.
Usage or enterprise licensing, depending on throughput, hosting, support and integration needs. Tell us your monthly case volume and average pages and we scope a pilot. No per-call fees or SLA tiers are published; what we quote is written into the agreement.
Self-Service meters deduplicated pages from 10 cents down to 5 cents at volume, duplicates never billed; the 2 annual licenses are on the pricing page. API partners usually land on a license.
API and integrations, answered.
Let's design the integration around your product.
Tell us what your product does and what it needs from the record. The technical team replies with the next step: a fit call, documentation eligibility, or an honest "not yet".
No patient records, names or case details in this form. Secure intake instructions come after the first call. Prefer email? aj@medrecords.ai.
Thanks. The technical team has it.
You will hear from aj@medrecords.ai with a proposed fit call and what to bring to it. If a calendar is faster, pick a 30-minute slot and mention the API.