Public intake
Capture partner inquiries and data requests through controlled public forms.
POST /api/v1/public/partner-leads
POST /api/v1/public/compliance-requests
Integrations
Know what your team will receive before you connect.
Hospitals and partners can review the schema, starter collection, and sample payloads before deciding how MedDossier will hand off prepared records.
Handoff kit
Three assets show the handoff before live data is used.
OpenAPI schema
See the available intake, packet sharing, callback, and export routes before credentials are exchanged.
Postman starter collection
Run the main requests for login, public intake, secure sharing, hospital callbacks, and export examples.
Example payloads
Inspect the sample callbacks, case summary metadata, and FHIR export so your team knows what arrives downstream.
Coverage
The assets answer three practical questions.
Use them to confirm how requests are captured, how packets are prepared, and how finished records reach your team.
Packet preparation
Support sign-in, account recovery, key case edits, and final packet approval before handoff.
POST /api/v1/auth/login
POST /api/v1/auth/password-reset/request
POST /api/v1/auth/password-reset/confirm
POST /api/v1/orders
POST /api/v1/orders/{order_id}/files
GET /api/v1/orders/{order_id}/patient-review
PATCH /api/v1/orders/{order_id}/patient-review
Hospital handoff
Create upload invitations, issue expiring share links, send callbacks, and export prepared case data.
POST /api/v1/hospital/trigger-upload
POST /api/v1/orders/{order_id}/share
POST /api/v1/hospital/orders/{order_id}/dispatch-webhook
GET /api/v1/hospital/orders/{order_id}/fhir-bundle
What You Can Check
Review the exact outputs before live connection work starts.
The published schema, collection, and examples are enough to confirm fit with intake, security, and receiving-team expectations.
Access is separated by route so patient actions, packet preparation, and hospital handoff do not share the same credential path.
The starter collection includes account recovery requests so partner reviewers can test common access issues before go-live.
Public forms create a follow-up record, not a loose email thread, so requests can be tracked to the next action.
Hospital handoff currently focuses on secure share URLs and a compact FHIR bundle for prepared records.
Examples
Inspect sample payloads before live credentials are issued.
Upload invitation webhook
Shows what a hospital receives when a patient is invited to upload records.
Packet shared webhook
Shows the callback sent after a prepared packet is approved for secure sharing.
Sandbox summary
Shows reusable case metadata, including order IDs, URLs, and delivery status fields.
Available Now
Enough to decide the next integration step.
Base domain: meddossier.com
Interactive docs: `/docs`
Schema: `/openapi.json`
Static schema: `/openapi/meddossier-openapi.json`
Collection: `/meddossier-postman-collection.json`
Examples: `/integration-examples/*`
Before Go-Live
Direct partner confirmation is required before go-live.
Live endpoint credentials, callback acknowledgement rules, and receiving-team owners.
Production SSO, SDK requirements, or customer-specific API contract language.
SLA, retention, and compliance terms beyond the standard controls shown on the site.