By Waqar Ilyas · Published · Sources checked 2026-10-23
Organization and education. Not clinically reviewed.
Begin with the purpose of the visit
When appointment time is limited, a long export can obscure the question you most want answered. Begin with the reason for the visit and the concerns you want to raise. Then select the records that make those concerns easier to describe.
A summary is a navigation aid, not a complete medical history or a diagnosis. The relevant professional may need different information or a different format. Ask in advance if a clinic has a preferred way to receive records.
Communication research is about more than a document
Patient- and Family-Centered I-PASS research studied a hospital communication program involving families and clinical teams. Such programs include practices and interactions around information, not simply a printable page. [1]
The distinction matters. We can take care in structuring a summary without claiming that a Vayvi export reproduces a research intervention or its outcomes. The template here is an organizational suggestion.
Select the relevant period and records
Choose a period that relates to the question, and state why you selected it. Include original dates and units. If information is incomplete, note that clearly. A summary of partial records should not appear to describe every event.
For example, a family discussing a recent observation may select a few relevant entries and one source document. Exporting every unrelated record can make the important details harder to find and share more private information than necessary.
Separate facts, uncertainty, and questions
A fact might be a recorded measurement with its date. Uncertainty might be an approximate time or an incomplete day of logging. A question asks what the family wants help understanding. Keep each recognizable.
Avoid adding an inferred cause as though it were an established finding. If an interpretation matters to you, frame it as a question for the professional. Preserve the original source so a reader can check what was actually recorded.
A one-page example
Fictional example: a summary names the profile, visit date, two questions, a selected period of records, known gaps, and one relevant document. A final space is left for the outcome and next action.
The first lines should tell the reader why the page exists. The body should be legible without tiny type. Chart images need labels and enough context to understand the dates and units. If a chart adds little, use a small table instead.
- Reason for the visit and the questions to discuss.
- Selected factual records, with dates and original units.
- Gaps, estimates, or conflicting information.
- Relevant documents and existing instructions.
- Agreed next step, completed after the conversation.
Preview before you share
Check the selected person, date range, recipients, and included fields. Remove information unrelated to the purpose. Private recovery or screening history should not be included in a household report by accident.
A downloaded document can leave the access controls of the app. Verify the destination and the clinic’s preferred sharing method. Keep the copy somewhere you can find it, and do not assume removing app access retrieves a previously shared file.
Close the loop after the visit
Record the instructions actually given, their source and date, and the next agreed action. Clarify anything you did not understand through the provider’s appropriate contact route. Do not rely on an old draft once new instructions exist.
In Vayvi, preview a report before sharing and keep relevant original entries available. A useful summary is concise, accurate, and explicit about uncertainty. It should help you ask your question, not answer it on behalf of a clinician.