Translation, source index, and record summary: three different jobs
Translation changes language, a source index shows where each file or statement came from, and a record summary condenses selected information for navigation. A usable packet may need all three, but none should silently replace the originals.
Build the layers in the right order
Start with originals and a source index. Translate the content requested by the receiver while preserving dates, units, names, and uncertainty. Write a concise summary only after the source map exists, and link important summary statements back to files and pages.
A practical order of work
- Preserve originals.
- Build the source index.
- Confirm translation scope.
- Link summary statements to sources.
- Label patient context and uncertainty separately.
What each layer actually does
Makes selected source content readable in another language.
Maps dates, institutions, filenames, pages, languages, and status.
Provides a short navigation view of selected source-supported information.
Remain the evidence layer and should not be overwritten.
Who this comparison helps
- Choosing a preparation service.
- Explaining deliverable layers.
- Reviewing a bilingual packet.
Clear medical boundaries
- MedDossier does not diagnose.
- MedDossier does not provide treatment.
- MedDossier does not recommend hospitals.
- MedDossier does not promise admission.
What to avoid
- Calling a translation a complete packet.
- Writing a summary before mapping sources.
- Presenting patient recollection as source-record text.
Questions patients often ask
Can a summary replace translation?
Only if the receiver explicitly accepts it; otherwise the requested source documents may still need translation.
Can a source index replace originals?
No. It is a navigation layer over the original records.
External sources
Check which layer your packet is missing
Describe the purpose, language, and current file set before sharing sensitive records.
Start free record check