01
Who this handbook is for
Use this as a starting point if you want to understand the record scope before choosing a next step.
Patients preparing records for overseas care intake
Patients preparing records for specialist review or second-opinion preparation
Family members or caregivers authorized by the patient to find and organize records
People who want to identify available, missing, and uncertain records before deciding whether to share
If you are experiencing an emergency or need diagnosis, treatment advice, prescriptions, or emergency arrangements, contact a qualified local medical service. MedDossier is not an emergency or medical-advice service.
02
Answer five questions before organizing files
Set the scope before translation or upload. Writing down these five items helps define the first set of records to prepare.
- 01
What is the packet for?
State whether it is for intake preparation, specialist review preparation, second-opinion preparation, or care handoff. Organize existing records without asking the packet to make a medical judgment.
- 02
Who is the expected receiver?
Record the public requirements of the hospital, department, specialist team, or other receiver. If the receiver is not confirmed, do not assume every organization wants the same files.
- 03
Which languages are needed?
Confirm the source and target languages, and whether originals plus an English summary are requested. The receiver decides whether certified translation is required. A preparation draft should not be described as a certified translation by default.
- 04
When are the records needed?
Record the intake, review, or handoff date. Prioritize by purpose and relevance instead of processing an entire history before the scope is clear.
- 05
What is available and what may be missing?
Classify records as available, missing, uncertain, or to be requested. Keep gaps visible and confirm requirements with the receiver.
03
Build a cross-border record checklist
These categories are a starting point, not a judgment of medical sufficiency and not a replacement for receiver-specific requirements.
Course and visit records
- Look for
- Discharge summaries, clinic notes, referral letters, history summaries
- Keep
- Date, organization, department, original title, file or page
Tests and reports
- Look for
- Laboratory, pathology, imaging, and functional test reports
- Keep
- Test name, value, unit, reference range, date, and source
Procedure and treatment records
- Look for
- Operation notes, procedure reports, treatment records, discharge medication lists
- Keep
- Original text, date, organization, and record type without rewriting treatment conclusions
Current information
- Look for
- Current medicines, allergies, and recent status
- Keep
- Separate source records from information supplied by the patient
Imaging materials
- Look for
- CT, MRI, ultrasound reports, and image files requested by the receiver
- Keep
- A report does not replace original images when the receiver specifically asks for them
Handoff context
- Look for
- Purpose, receiver, languages, timing, and authorization scope
- Keep
- Store separately from medical records so it can be updated
04
Build seven checkable layers, not just a folder
A packet can include the seven parts below. The actual scope depends on available records, language needs, and the agreed preparation scope.
Packet cover
State the purpose, covered scope, languages, preparation date, version, and non-medical boundary.
Patient-visible summary
Introduce the structure, point important content to sources, and separate patient-supplied notes from provider records.
Timeline
List record events, source organizations, record types, file or page references, and translation or confirmation status by date.
Source index
Preserve file names, dates, organizations, and pages so key content can be checked in its original context.
Bilingual content
Keep source text aligned with translation, dates, units, reference ranges, and uncertainty flags. Mark unclear text for confirmation.
Missing and uncertain items
Show missing originals, incomplete scans, unclear dates or units, patient recollections, and receiver questions.
Patient review and sharing settings
The patient or authorized representative reviews the version, then separately confirms the receiver, scope, duration, download, forwarding, and revocation path when supported.
Source traceability helps a reader return to the original file and context. It does not prove that the record set is complete, medically correct, clinically sufficient, or accepted by the receiver.
How to read the synthetic packet example
SYN-MD-001 shows the difference between scattered files and a checkable packet. It adds structure, not new medical facts.
View synthetic sample packetsBefore
- File names have no date, source, or type
- Provider records and patient notes are mixed
- A referenced but unavailable report is hidden
- English excerpts do not map back to source files
After
- Cover and boundary
- Patient-visible summary and timeline
- Source index and bilingual preparation draft
- Missing items, uncertainty, and sharing settings not activated
The sample is not a real patient case. It does not prove receiver acceptance, medical quality, clinical outcomes, regulatory approval, or approval of real-record upload for any jurisdiction or scope.
05
Keep upload, processing, and sharing separate
Explain each sensitive step and let the patient choose before moving forward. Upload applies only if it is within the approved service scope at that time.
| Stage | What happens | What it does not mean |
|---|---|---|
| Free precheck | Describe the purpose, receiver, language, timing, and record scope | No file upload and no automatic paid work |
| Upload, only when approved scope allows | Add files for packet preparation | Not authorization for external sharing, and not evidence that every jurisdiction or cross-border PHI scenario is supported |
| Processing | Order files, extract content, prepare translation, build an index, and flag gaps | Not confirmation by a doctor |
| Patient review | Check content, sources, and uncertainty | Not a waiver of correction or deletion requests |
| Final confirmation | Confirm a prepared version | Not permission for indefinite access |
| Authorized sharing | Specify the receiver, scope, duration, and control settings | Not proof that the receiver accepted the case |
- Stage
- Free precheck
- What happens
- Describe the purpose, receiver, language, timing, and record scope
- What it does not mean
- No file upload and no automatic paid work
- Stage
- Upload, only when approved scope allows
- What happens
- Add files for packet preparation
- What it does not mean
- Not authorization for external sharing, and not evidence that every jurisdiction or cross-border PHI scenario is supported
- Stage
- Processing
- What happens
- Order files, extract content, prepare translation, build an index, and flag gaps
- What it does not mean
- Not confirmation by a doctor
- Stage
- Patient review
- What happens
- Check content, sources, and uncertainty
- What it does not mean
- Not a waiver of correction or deletion requests
- Stage
- Final confirmation
- What happens
- Confirm a prepared version
- What it does not mean
- Not permission for indefinite access
- Stage
- Authorized sharing
- What happens
- Specify the receiver, scope, duration, and control settings
- What it does not mean
- Not proof that the receiver accepted the case
07
Seven common mistakes and safer corrections
Mistake
Upload every file before defining the purpose
Correction
Write down the purpose and receiver, then choose the first records
Mistake
Keep the translation but discard the original
Correction
Keep originals and map key translated content back to sources
Mistake
Mix patient recollection into provider records
Correction
Label source records and patient-supplied notes separately
Mistake
Guess when a record is missing
Correction
Mark it missing, unclear, or pending confirmation
Mistake
Present record preparation as a second opinion
Correction
Use second-opinion preparation or record-review preparation; qualified professionals provide medical opinions
Mistake
Assume upload allows sharing with anyone
Correction
Make external sharing a separate authorization step
Mistake
Use a synthetic sample as outcome proof
Correction
Use the sample only to explain structure, not results or receiver endorsement
08
Frequently asked questions
Should I translate every medical record?
Not necessarily. Confirm the receiver's requirements, the purpose, and priority records first. Receiver rules and actual scope determine whether full or certified translation is needed.
Can I start with the free precheck and decide later?
Yes. The free precheck does not upload files. After completing it, you may continue to the separate upload page, subject to the instructions then shown, to prepare records, receive a page-based quote, and decide whether to pay. Whether real records are appropriate for upload depends on the relevant jurisdiction, patient authorization, record scope, and applicable data-processing conditions; upload and external sharing remain separate steps.
What if a report is missing?
Mark it as missing or uncertain and record where it was referenced. Do not invent its contents or assume the receiver does not need it.
Does source traceability mean every sentence is accurate?
No. Traceability helps the reader return to the original file and context. It does not prove completeness, medical correctness, or receiver acceptance.
Will MedDossier tell me which hospital to choose?
No. MedDossier supports record organization, translation preparation, and patient-controlled sharing. It does not recommend hospitals or doctors.
Is a record packet a formal second opinion?
No. A packet can support second-opinion preparation. A qualified medical professional provides the actual medical opinion.
Public source notes
The original links are listed below. This page does not restate or expand their record-rights, legal, or checking claims.
- Your Medical RecordsU.S. Department of Health and Human Services
- Get It, Check It, Use ItHealthIT.gov
- Check ItHealthIT.gov
The U.S. government sources are used only as general background for obtaining and checking records. They are not legal advice, do not determine rights in any jurisdiction, do not imply agency endorsement of MedDossier, and do not prove medical sufficiency. Read each original page and its stated scope directly.
Continue checking your preparation scope
Source-linked bilingual record packet
See how a source index and bilingual content stay aligned.
Cross-border record checklist
Inventory available and potentially missing records by category.
Upload and authorized sharing
Understand why upload, review, and sharing remain separate.
Sample packet anatomy
Use synthetic, no-PHI material to understand packet structure.
Source index and timeline
Read more about two record-navigation structures.
Missing-item flags
See how missing and uncertain items remain visible.
Trust Center
Review public data-handling boundaries and request paths.
Primary accessible version
This HTML page is the handbook's primary accessible version. A PDF is only a visual and print companion; it does not claim PDF/UA, Tagged PDF, or WCAG conformance without structural tagging and manual screen-reader evidence.
https://meddossier.com/resources/cross-border-record-preparation-handbookOperator and support
MedDossier is operated by AssetGrid LLC in the United States.