Cross-border medical record packets
Trust Center
MedDossier prepares records for review. It does not replace doctors, promise admission, or share records outside the scope the patient authorizes.
Public controls
Records are prepared for the selected scope. Hospital contact or family updates require explicit authorization before that work starts.
Authorization template
Patient, exception QA, operations, translator, and hospital-facing views stay separated so each person sees the right part of the case.
Security controls
Deletion, correction, billing, and privacy concerns use a tracked request path instead of loose inbox follow-up.
Open request
Data Lifecycle
This is the public control map for patients, families, hospitals, and partner teams reviewing whether MedDossier is the right path.
Data type
Purpose: Route the case, prepare the packet, and keep the authorized contact informed.
Access: Patient or authorized contact, MedDossier case team.
Retention: Reviewed with the case record and request history.
Request path: Correction or deletion request
Data type
Purpose: Extract, translate, organize, and check source material for packet preparation.
Access: Authorized case team with role-limited access. Translators see structured source text, not raw files.
Retention: Configurable retention window after delivery unless a request or agreement changes it.
Request path: Deletion or access review
Data type
Purpose: Give the next doctor, hospital, coordinator, or partner team a clearer first read.
Access: Patient, authorized contacts, and approved hospital or partner recipients.
Retention: Retained while delivery, sharing, and follow-up remain active.
Request path: Sharing or deletion review
Data type
Purpose: Show what changed, when links were created, and where follow-up is needed.
Access: MedDossier operations and authorized case viewers when relevant.
Retention: Kept with the case history for accountability and support.
Request path: Access or privacy concern
Routes
Different requests need different handling: patient uploads, partner reviews, and privacy questions each start from the path built for that work.
Start here when you want to understand what happens before uploading medical files.
Patient path
Review packet quality, API assets, retention expectations, and partner-specific questions before deciding whether MedDossier fits the program.
Partner path
Use one tracked form when a case needs deletion, correction, access review, billing review, or other follow-up.
Open request
Trust Library
The Trust Center keeps the high-level answer in one place, then links to the pages that carry the operating details.
Role separation, expiring share links, exception QA, and retention review.
What data is collected, how it is used, who can access it, and how requests work.
Deletion, correction, privacy, billing, and partner request paths.
Service boundaries and public terms for using MedDossier.
Answers before upload, delivery, partner review, and data requests.
OpenAPI, Postman, webhook, and FHIR handoff assets for partner review.
Next step
Upload records when the case path is clear. Use partner review when a team needs to evaluate packet quality, workflow fit, or integration readiness first.