Reports & summaries

What Reports is for

Reports is where your record becomes something you can hand to a clinician. Instead of arriving at an appointment with a phone full of PDFs, you walk in with a tidy packet: a short brief of what is relevant, the questions worth asking, and the supporting labs, wearable trends, and medications attached. Everything here is a draft you prepare and own. Ojava does not send anything, order anything, or get anything signed.

Your record at a glance

The top of the page summarizes what you have on file: how many imports you have brought in, how many results have been accepted into your record, and how many current medications or supplements are available from your Profile list or imported medication rows. These counts tell you, in one look, how complete the picture is that any packet would draw from.

Packet drafts from your records

Reports assembles preparation packets for common purposes, each built from the data you have accepted: a general visit brief, condition-specific prep, medication, lab-result, or specialist conversation context, reproductive, fertility, pregnancy, or postpartum questions, and a local escalation handoff packet. Some packets can be copied, exported, or printed directly from Reports; others can be opened in Ojava Coach to draft the narrative and questions. Every packet is a preparation aid for your own use and for sharing with a clinician, not a clinical order.

Ojava Coach also receives a weekly healthspan habit report from the same report family. It can summarize accepted biomarkers, wearable sleep and recovery rows, nutrition and water logs, workouts, fasting windows, mood check-ins, and wellness sessions without requiring an active goal first. The report names which domains are ready, which are still building, what is missing, and one next habit to keep the week grounded. It is general wellness context only, not diagnosis, lab ordering, disease-risk scoring, medical nutrition therapy, a training prescription, or a care decision.

The reproductive prep packet uses the same consent-gated clinical prep inputs as the rest of Reports: cycle logs, symptoms, goals, procedures, appointments, medications, supplements, allergies, accepted record rows, and related lab or vital context when they are present. It names which sections are ready and what is still missing before a clinician visit. It does not predict fertility, manage pregnancy, prescribe contraception, give obstetric advice, order tests, interpret fetal or pregnancy risk, diagnose, treat, or replace your clinician.

Chronic illness visit brief

For people tracking a long-running or fluctuating condition, Reports can build a chronic illness visit brief from the trackers you already use: daily check-ins, symptoms, flares, flare recovery, mood, energy, stress, medication routine, treatment-response notes, food timing, sleep, and wearable recovery when those records are present. The brief is designed for a short appointment: what changed recently, which worksheet-style sections are ready to print, whether your between-visit profile is consistent enough to review, what may have triggered a harder stretch, which co-occurring contexts are worth tracking around high-symptom days, which symptom category needs the clearest tracking prompt, which condition-aware tracker lanes are ready when your notes name a chronic condition, what helped, what is missing from the record, de-identified peer-support prep, and the questions to bring into the room.

The chronic brief uses the same deterministic calculators that Ojava Coach sees, including symptom burden, daily check-in continuity, a worksheet checklist, trigger context review, condition-aware tracker guidance, symptom-specific prep, flare recap, flare recovery-window context, mood and stress rhythm, hard-day pacing, medication routine completeness, dose history, treatment-response prep, food and symptom timing, readiness, sleep debt, training load, and recovery signal consistency. The condition-aware tracker guidance uses your own symptom notes, mood and energy check-ins, food timing, routine timing, and wearable context to say which lanes are ready for conditions such as ME/CFS, long COVID, POTS, fibromyalgia, migraine, IBD, endometriosis, and related chronic patterns. It is still tracking and visit-prep context only. The trigger section compares high-symptom days with nearby self-reported and wearable context for clinician questions, not a claim that any context caused the symptoms. The treatment section compares record timing around a logged medication or supplement start date for clinician questions, not a claim that a treatment worked, caused a side effect, or should be changed. The recovery signal consistency section tells the report when supportive and strained recovery signals should be shown together instead of condensed into one headline. The food timing section is a same-day association summary for clinician questions, not a claim that a food caused a symptom. The peer-support section drafts safe discussion themes, neutral questions, and redaction reminders for community conversations. It does not create a public post, match you with peers, send a message, or share medication details, dates, contact information, record numbers, clinician names, or other identifying details by default. If one of those inputs is missing, the report says so instead of filling in a fake value. You can copy the brief or open a printable version from the Reports page. If you ask Ojava Coach for a chronic illness report, flare worksheet, or visit brief, Coach receives the same readiness label, missing-input list, clinician-question list, symptom and trigger summary, and report boundary before drafting. If you are not signed in yet, the public chronic symptom and flare worksheet can organize a lightweight episode timeline, possible trigger-review prompts, recovery notes, and visit questions without creating a private tracker record.

The public condition prep directory now includes chronic entry pages for ME/CFS, long COVID, POTS, fibromyalgia, migraine, and IBD. Those pages explain what to track, which records to bring, how to start with a no-account assessment or chronic flare worksheet, and how a signed-in Reports brief can support the next clinician conversation.

Weight-care and GLP-1 visit prep

Reports also includes a weight-care prep brief for a clinician conversation about weight, metabolic health, or GLP-1 questions. It gathers the tracker context you already keep in Ojava: food entries, water logs, weight and waist measurements, workouts, current medications and supplements, routine events with review notes, Profile GLP-1 support notes when present, GLP-1 dose-log fidelity for latest self-reported status, timing, injection or location notes, and next schedule checks, and diary-native GLP-1 context that lines routine days up with food entries, calories, protein grams, water, digestive or appetite notes, body trend or same-day weight rows, and workout entries when those rows exist. It also keeps reviewed MyFitnessPal import provenance in the same brief when food, water, exercise, or progress rows came from a reviewed CSV import, plus recent symptom notes such as digestive or appetite concerns. The card separates what is present from what is missing so you know whether to add food, water, body, medication-routine, or symptom context before a visit. It also calls out GLP-1 prep checks for appetite or digestive notes, protein grams, hydration logs, and medication-routine review notes so the brief is easy to tighten before the conversation.

The brief is preparation only. Ojava does not decide whether a GLP-1 is appropriate, prescribe one, set a dose, change a medication, diagnose obesity or diabetes, explain what caused a symptom, or create a treatment plan. It gives you a clearer record and a few questions to bring to your own clinician.

Acute GI and foodborne-illness prep

Reports can also prepare an acute GI brief when your own tracker rows include recent digestive symptoms such as nausea, vomiting, diarrhea, stomach cramps, or feeling sick after eating. The brief reuses the same deterministic acute GI prep packet that Coach sees: recent symptom entries, same-day food timing when logged, water-log context, current medication names, current supplement names, missing inputs, and questions to bring to a clinician.

This is organization for a conversation, not an answer about what caused the symptoms. Reports does not diagnose food poisoning or infection, prove food causation, assess dehydration, prescribe fluids or electrolytes, recommend antibiotics or anti-diarrheal medication, order stool tests or labs, detect outbreaks, report to public health, triage emergencies, book urgent care, or replace medical care.

Benefits and prior-authorization prep

Reports can also prepare a benefits and prior-authorization packet from payer-style records and the medication, service, referral, or visit context you already keep in Ojava. It separates plan or payer documents, medication context, and service details from the details you still need to gather.

Ojava checks payer documents for common call identifiers before it names gaps: plan or payer name, member ID, group number, plan phone or portal path, and claim, authorization, invoice, or account references. If one of those details is already present, Reports should not ask you to gather it again.

This packet is only preparation for your own call or clinician conversation. Ojava does not make a benefits decision, file requests, promise payment, replace your plan, or replace your clinician.

When your records include both an explanation of benefits and a provider bill or patient statement, Ojava can also prepare an EOB and bill reconciliation checklist. It helps you compare service dates, providers, facilities, amount-style fields, and reference numbers before you call the plan, billing office, pharmacy, or clinician office. It does not calculate an amount owed, decide coverage, file a claim, file an appeal, send records to a payer, give legal advice, or recommend payment.

Family benefits questions get a narrower readiness packet rather than a coverage answer. It composes family-building, maternity, newborn, pediatric, caregiver, dependent, EAP, and plan-call context from the same reproductive, family-pediatric, and payer-prep paths. Reports and Coach can name which lanes have evidence, which plan details are missing, which consent and audit placeholders would be needed, and what to ask before a user-controlled call. Ojava does not decide coverage, submit claims, submit prior authorization, choose a provider, book care, act for a dependent, guarantee benefits, or replace a plan, employer, clinician, or benefits administrator.

Escalation handoff packet

Reports also builds a local portable escalation handoff packet from the same accepted records. It combines the visit-brief data room, medication and lab discussion context, follow-up prep, open questions, attachments, and the first questions to ask next, then lets you copy the packet or export it as a .txt file from Reports. This is the “what changed, what to attach, and what to ask” layer you can review before sharing with your own clinician. It does not send a message, promise a clinician response, diagnose, prescribe, order labs, create a referral, or complete a care action.

If you have saved Coach threads, the same exported handoff can include a local message-history summary: saved thread count, user-written topics, AI reply count, safety replies, unresolved turns, and questions to verify before a visit. That summary is review prep only. It does not send a message, create a provider inbox, promise a clinician response, or prove a human clinician reviewed the thread.

The exported handoff can also include medication-burden review prep when your current medication and supplement list has enough context. Reports can name five-medication, older-adult, anticholinergic, symptom, duplicate-name, and medication-plus-supplement prompts, attach AGS Beers, STOPP/START, deprescribing, FDA, and DailyMed source links, and list questions to bring to a clinician or pharmacist. This is organization only. Reports does not score anticholinergic burden, classify Beers or STOPP/START issues, predict falls or cognition risk, prescribe, stop, start, taper, substitute, dose, time, approve refills, or claim medication safety clearance.

If you have source-provided home blood-pressure or glucose rows, the exported handoff can also carry the same log-readiness packets Coach sees. Reports counts paired BP days, morning and evening BP timestamp coverage, glucose reading days, morning and later-day glucose context, source labels, missing setup details, clinician questions, and linked AHA, USPSTF, ACC/AHA, MedlinePlus, ADA, CDC, NIDDK, and FDA source material. This stays log-readiness only: Reports does not diagnose hypertension, assign a BP category, set targets, validate measurement accuracy, diagnose diabetes or prediabetes, grade glucose control, define personal ranges, recommend insulin or medication changes, send warnings, monitor emergencies, or decide care.

Reports now includes a compact clinical-history portability summary in that same local handoff: accepted row counts, record-family breadth, dated and coded rows, document-reference counts, family-history context, care-plan and goal counts, missing source inputs, review questions, and the artifact boundary. Settings still owns the durable health-data package export when you need the full clinical-history.json artifact for encounters, conditions, immunization history, family-history context, service requests, care plans, goals, and document-reference metadata. Reports keeps the local handoff copy focused on visit prep and does not turn family history into patient conditions, risk scoring, screening decisions, provider messaging, vaccine decisions, or completed clinical action.

When accepted records include add-on lab markers, imaging or procedure reports, screening context, family-history clues, symptoms, or visit goals, that handoff can include an add-on lab and imaging prep section. It names discussion topics, source-evidence counts, missing information to confirm, research sources for report organization, and clinician questions from your accepted records. Coronary CTA, CAD-RADS, plaque, stenosis, and calcium-score report language is organized using the uploaded report text and the CAD-RADS 2.0 source, but Ojava does not order labs or imaging, make screening decisions, interpret images, calculate plaque or event risk, recommend medication, claim clinician review, or provide access to outside tests or scans.

Reports also carries a whole-health protocol and marketplace-prep section into the local handoff export when enough reviewed context is present. It organizes records, labs, wearables, nutrition context, goals, and supplement or routine questions into packet sections, a marketplace-prep checklist, review questions, and external-review package readiness. That package names ready data areas, missing attachments, user-controlled sharing actions, disabled outside-service actions, and the review-only boundary you can bring to an outside service or your own clinician. It is still preparation only: Ojava does not diagnose, prescribe, order labs, sell testing, write a protocol, approve supplements, connect outside-service accounts, or claim clinician review.

The handoff can also include a deterministic second-opinion record packet. It gathers accepted records and results, treatment or procedure timeline context, medication, supplement, and allergy context, background history, and the questions you want an outside reviewer to understand. This is a local packet you review before bringing it to your own clinician or outside reviewer. Ojava does not render the second medical opinion, recommend treatment, override a treating clinician, order tests, send records, or claim clinician review.

The handoff can also list outside-provider selection prep: specialty goals, user preferences, candidate profile details to review, source context to bring, and questions to ask before you choose where to book outside Ojava. Ojava does not choose a provider, create a referral, confirm coverage, book a visit, message a clinician, or promise a clinician response.

A portable emergency card reuses this same handoff family. Instead of creating a separate emergency profile, it gathers user-reviewed identity, allergies, medications, supplements, conditions, emergency contacts when present in source rows, and recent timeline context into compact local card text that you can copy or export after reviewing. It is not a provider inbox, QR handoff, live sharing link, or emergency triage tool. Accepted FHIR RelatedPerson rows can fill that contact section only when the reviewed source labels the relationship as an emergency contact; Ojava keeps the contact value bounded to source metadata such as relationship and method count instead of exposing raw phone or email values. Reports and Coach can also name printable-card readiness for that local card: whether allergies, medications, emergency contacts, conditions, and latest context are present enough for a short print or export review. This remains local prep only, not QR sharing, a live sharing workflow, provider inbox delivery, permissions, external messages, triage, or a care decision.

Care-plan follow-up readiness uses the same local packet. When your accepted records include care-plan, goal, visit, service-request, medication, symptom, wearable, or document context, Reports can organize what changed, whether explicit follow-up timing or encounter context is present, and what source details are still missing before a follow-up visit. A packet is marked ready only when the accepted rows include an anchor, follow-up timing or encounter context, a dated timeline, and a source file or import. It is visit prep and education only: Ojava does not create or complete a care plan, change clinician instructions, monitor you remotely, message a clinician, route a referral, prescribe, order labs, diagnose, create a treatment plan, or prove clinician review.

Post-visit instruction readiness extends that lane for accepted after-visit summaries and discharge instructions. It organizes the follow-up tasks, medication-change mentions, pending tests or referrals, warning-language excerpts, dated source evidence, and missing details you may want to confirm from the original source. It is a review checklist only: Ojava does not change instructions, give medical advice, triage symptoms, monitor emergencies, send messages, contact clinicians, route referrals, prescribe, or order labs.

Missing-information response prep belongs in that same follow-up lane. If a packet shows gaps, Reports can turn them into a local checklist you review yourself: what detail is missing, which accepted source raised the question, and how you might ask about it at the visit. Ojava does not send that checklist, contact a clinician, change clinician instructions, route care, monitor your health, diagnose, prescribe, order labs, create a treatment plan, or prove that a clinician reviewed anything.

FHIR document references use the same local-review boundary. When accepted rows include document-reference metadata, Reports and Coach can organize the title, type, category, date, source trail, and attachment pointer presence before a visit. They do not read embedded attachment content, interpret images or scans, send records, decide coverage, or prove clinician review.

The questions in the handoff are now ranked from the strongest visit-prep signals first: recent symptoms, your stated goals, medication-list gaps, older or missing record categories, source-quality issues, prep-lane gaps, and consented wearable context when present. Each question includes a short reason so you can see why it rose to the top before you copy or export the packet. This is question organization only. It does not diagnose, triage, decide urgency, prescribe, order labs, create referrals, create a treatment plan, or promise that a clinician will act.

Next steps and blockers

Because a packet is only as good as the record behind it, Reports shows the local next steps and blockers for each draft: what is ready, and what is still missing (a result not yet accepted, a medication without a dose, a measurement that is stale). These are completeness checks on your own data, the things you would want to fill in before a visit, not gates imposed by a clinician.

The Visit readiness section does this for service-specific packets: primary-care visit prep, refill conversations, lab-order conversations, preventive checkups, weight-care prep, and mental-wellness conversations. Each card names the context already present and the fields still missing before that conversation would be easier to prepare.

Communication prep

Reports also prepares the communication side of a visit: record-change review, follow-up question prep, continuity timeline, appointment preparation, and language-access prep. When clinical-context consent is active, these cards can use accepted records plus recent wearable trends, such as sleep, HRV, resting heart rate, steps, or other supported wellness rows. Wearable context is only used to make the question list and visit message more complete. It is not an alert, diagnosis, treatment recommendation, or promise that a clinician has reviewed the data.

Ojava Coach can also compose the same communication prep with appointment prep and practical logistics when you ask for a portable appointment handoff packet. The packet is a local review aid for what to bring, what to ask, and what communication support to prepare. It does not send a message, route an interpreter, provide translation, book or join a visit, arrange transportation, certify an accommodation, verify coverage, submit a claim, or deliver anything to a clinician.

The same continuity timeline can now appear in Ojava Coach when you ask what changed, what to carry forward, or what belongs in a next-visit handoff. It reuses the Reports continuity builder: accepted record anchors, repeated lab or vital changes, current medication names, open questions, and recent record activity. It stays patient-controlled continuity prep: local review, no completed care action, and no proof that a clinician reviewed the timeline.

Medication, lab, and specialist conversation prep

Reports can organize medication-list questions, lab-result context, and specialist-visit questions into a local packet. It shows which source records are present and what you may want to confirm before a conversation. Ojava does not create a refill request, lab request, specialist referral, prescription, order, approval, or clinician handoff.

Medication readiness now uses both accepted medication imports and the current medications and supplements you keep in Profile. Reports deduplicates matching names, shows where each item came from, separates supplements as review context rather than pharmacy-routed prescriptions, and keeps item details out of packet prep until clinical-context consent is active. Ojava Coach also gets a name-only reconciliation line when accepted imported medication-list rows and current Profile medications need comparison, including Profile-only, imported-only, duplicate-name, and detail-mismatch review flags. Accepted FHIR medication dispense and administration rows can add medication-history context, but they do not prove pharmacy fulfillment, administered care, adherence, clinician review, or a medication change. Their names and codes may come from companion FHIR Medication support resources, which are not Reports rows by themselves.

Reports also uses the health-history trackers you keep on Timeline and Profile when clinical-context consent is active: allergies, immunizations, family history, procedures, symptoms, goals, medications, and supplements. That means a family-care, pediatric, specialist, procedure, or post-visit packet can reflect your own maintained record even when those details did not arrive through an imported file. Without clinical-context consent, those tracker details stay out of packet prep.

Accepted FHIR and C-CDA encounters, procedure history, medication dispense or administration history, service requests, care plans, goals, related-person contact context, specimen context, bounded Device source context, bounded Provenance source-lineage context, and document references count as supporting history for these packets. They help Reports name what happened, what source file it came from, and what to ask next. They do not clear procedures, order imaging, create referrals, decide coverage, complete care plans, complete goals, prescribe, prove medication fulfillment, prove administered care, prove adherence, or prove that a clinician reviewed an attached document. Specimen context is lab provenance only, not sample adequacy, lab validation, diagnosis, retest advice, collection instruction, or care guidance. Related-person context is contact and caregiver context only, not emergency sharing, consent proof, messaging, provider access, clinical relationship validation, caregiver invitation, or care guidance. Provenance context is source-lineage review only, not authenticity validation, consent proof, chain of custody, source correctness, clinician review, clinical validation, authorization, or care guidance. Device context is source-device review only, not pairing, live sync, monitoring, alerts, device control, medical-device validation, recall advice, warranty guidance, source correctness, clinician review, diagnosis, or care guidance.

The local handoff packet also checks multimodal visit-attachment readiness. It can organize outside-record labels, clinician notes, photo or image metadata, and video or voice-note labels when they are accepted in Ojava. This is organization and visit-prep context only. Reports does not interpret images, transcribe audio or video, send messages, create a provider inbox, claim clinician review, diagnose, prescribe, order labs, or promise a clinician response.

Care navigation readiness

Reports also shows care-navigation prep for second opinions, prior authorization, insurance and benefits questions, family or pediatric visits, fertility and pregnancy visits, and post-visit follow-up, including care-plan follow-up organization when those accepted rows are present. Each card lists the context already present in your records and the details still missing before a useful packet could be drafted. Family and pediatric prep separates caregiver or dependent context, immunizations, allergy and medication context, symptoms and questions, growth, development, school, feeding, sleep, documents, prior history, and follow-up items into named sections. Family-benefits readiness can then combine that family packet with reproductive and payer context for benefits-call prep across family-building, maternity, newborn, dependent, caregiver, and EAP lanes. This is preparation only: Ojava does not submit prior authorization, decide coverage, create referrals, give pediatric or obstetric advice, request prescriptions or labs, render second opinions, or change clinician instructions.

Calculator and questionnaire input readiness

Reports also shows which inputs are already on file for clinician-used calculator or questionnaire conversations, including cardiovascular calculator inputs, diabetes-screening context, sleep-questionnaire context, medication-safety context, and mental-wellness questionnaires such as PHQ or GAD-7 when those records are present. Accepted FHIRQuestionnaireResponse imports can count as questionnaire input context after review, while still staying out of score interpretation. Each card separates present inputs from missing inputs so you know what to fill in before a visit. This is an input checklist only. Ojava does not calculate or interpret clinical screening scores, decide whether a sleep study is needed, diagnose a mental health condition, assess crisis risk, rate medication safety, or tell you what care to get.

Preventive checkup prep uses the same readiness lane. It separates age and sex context, family-history details, immunization history, prior screening or procedure history, medication and allergy context, recent vitals or body measures, recent lab context, and the questions you want to raise at the visit. This is a completeness profile for a clinician conversation, not a due-or-overdue schedule, vaccine decision, genetic-test decision, lab order, procedure order, or clinical risk score.

Reports also carries rare-disease diagnostic-odyssey prep into the local clinician handoff export when accepted records include genetic, genomic, phenotype, family-history, or prior-workup context. The packet cites the 2026 NEJM AI rare-disease reanalysis study and OpenAI study summary, then lists source-report labels, phenotype clues, family context, missing inputs, and questions for a licensed genetics or specialist visit. It does not diagnose, interpret variants, classify variants, calculate genetic risk, recommend testing, order tests, send referrals, or claim clinician review.

Cardiology ownership packets use the same local handoff path. When accepted records include ApoB, Lp(a), hs-CRP, CAC, coronary CTA, CAD-RADS, plaque, stenosis, coronary-calcium context, FAI, perivascular fat attenuation, PCAT, coronary-inflammation report language, stress-test, nonobstructive-CAD, INOCA, microvascular-angina, coronary-flow-reserve, vasospasm, or cardiology-specific family-history or symptom clues, Reports can export the source labels, citation links, missing inputs, and cardiologist questions together. The export cites cholesterol and non-HDL source references when standard lipid rows are present, ACC/AHA risk-enhancer sources, a European Heart Journal ApoB discordance source when ApoB is reviewed beside LDL-C, non-HDL-C, and triglycerides, and the CAD-RADS 2.0 source, plus CRISP-CT FAI sources when coronary-inflammation language is present, the AHA/ACC chest pain guideline source, and an EAPCI INOCA consensus source. It still does not calculate ASCVD, PREVENT, MESA, plaque, FAI, coronary-inflammation, INOCA, microvascular, or event risk, diagnose coronary disease or ischemia, rule out heart disease, interpret images, set lipid targets, recommend medication, order labs or imaging, send referrals, recommend testing, or claim clinician review.

Same-day source refresh

A packet is most useful when its underlying records are current, so Reports flags when a draft is leaning on information that is worth refreshing before you rely on it. This keeps a brief you take to a visit from quietly going stale.

Source quality in the data room

Reports also shows a compact source-quality score for the record rows behind a packet. It looks at review state, dates, values, units, source breadth, record-type breadth, FHIR lineage, provider-ingest rows, benefits-only payer context, and standard coding for clinical rows, then names the first gaps to tighten before a draft becomes useful. The score is a completeness and provenance check, not a claim that a lab, medication, payer, or condition record is clinically correct.

When clinical-context consent is active, the data room can also show parser-loss repair context from the stored source datasheet, such as skipped rows that should be compared with the original export before a packet relies on nearby extracted data. Without that consent, Reports keeps those source details out of packet prep.

The data room also carries record-repair prompts from the same consented rows. If a common record category is older or not on file, Reports names the existing record to look for and the clinician question to bring, without deciding that a test, prescription, referral, or appointment is needed.

The source-quality improvement loop turns those gaps into a short prioritized repair plan. It ranks parser or feed failures, pending review rows, older source activity, missing lineage, canonical-event gaps, semantic mapping gaps, and weak field coverage so you know what to tighten first before copying or exporting a packet.

The same source workflow can include a stage manifest that shows which parts of the source pipeline are ready, need review, or are still missing. The manifest covers source feed accounting, row review, population-style transparency, the canonical event ledger, source identity consistency, longitudinal coverage, field coverage, semantic mapping, reconciliation conflicts, source-priority review order, whole-health source coverage, feed drift, the repair loop, and packaged export readiness.

You can copy or export a source-quality packet from this data room. The same packet is available in Ingestion once there is source data, so intake and Reports stay on one source-governance workflow. It includes the row-quality score, source-feed datasheet counts, parser-loss gaps, population-style source coverage checks, canonical health-event ledger, longitudinal source profile, same-day source-agreement profile, source identity consistency checks, reconciliation-conflict profile, source-priority review order, whole-health coverage profile, field-level source profile, unit-normalization readiness, source plausibility review for impossible dates, gross value shapes, unit mismatches, common lab-panel source-shape checks, and unchecked rows, semantic normalization profile, a source-cohort transparency card with included rows, excluded rows, candidate rows, exclusion reasons, source-trail counts, date window, replayable source cohort definition manifest, and a row-backed source cohort replay audit that uses the same reviewed package cohort shown in the data-room cards, records-search category counts, source-trail counts, imaging-report coverage, doctor-note coverage, report-document coverage, prioritized source-quality improvement loop, record-repair prompts, and next repair steps. Feed-drift review only appears after Ojava has a real prior source-quality snapshot to compare with the current one. It is a provenance artifact only, not proof that a result is clinically correct.

The source identity consistency section is deliberately narrow. It reports accepted source-trail breadth, aggregate subject-signature counts, dependent-context hints, generic source metadata, agreement checkpoints needing review, and reconciliation findings. It helps you decide what to inspect before a report blends source trails, but it does not prove identity, merge records, pick a winning source, anonymize data for research, diagnose, prescribe, order labs, or decide coverage.

You can save a source-quality snapshot from the data room when clinical-context consent is active. Ojava stores a minimized snapshot for future feed-drift comparison: aggregate source-quality counts, source-feed counts, row types, review state, dates, source lanes, and coding metadata. It does not store raw values, free text, filenames, source-file ids, import ids, receipt ids, source contract ids, hashes, storage paths, or original raw payloads in the snapshot history.

The data room also shows source contract receipt coverage. Receipts are compact machine-readable records for source type, license or access tier, fields, row counts, hash presence, evidence level, and limitations. They support data-governance review and export readiness, not clinical validation.

The population-style datasheet borrows the transparency shape used in serious health-data systems: source coverage, completeness, timeliness, cleanliness, and lineage. In Ojava it describes the sources behind your packet, not a research cohort, medical validation, monitoring result, or coverage decision.

The longitudinal source profile is also part of the packet. It summarizes dated windows, repeated concepts, source-trail continuity, and thin timeline areas so you can tell whether the rows support a review over time. It does not turn the packet into research data, monitoring, diagnosis, or a care decision.

The same packet now checks source agreement for accepted, dated concepts that overlap across source trails on the same day. Agreeing checkpoints can make duplicate-source review easier, while value, unit, text, or mixed-shape mismatches stay framed as source-review steps before a report or Coach answer relies on that detail.

The field-level profile groups the underlying rows by source and record type. For each group it checks whether dates, values, units, standard codes, and source lineage are present, then names the weakest field to review first. This helps you spot a thin lab export, medication file, provider feed, or benefits document before its rows travel into a packet.

The canonical event ledger turns the same reviewed rows into stable event domains such as labs, vitals, medications, conditions, encounters, and documents. It keeps the original source, code system, review state, syntactic readiness, semantic readiness, and quality gaps attached, so the packet can show what was normalized and what still needs source review. The semantic profile then summarizes code families such as LOINC, RxNorm, SNOMED CT, ICD, CVX, and UCUM, and names source-named concepts that still need coded exports when available.

What Ojava can prepare, and what it cannot

Ojava can prepare: a plain-language summary of what changed and why it might matter, the questions worth asking, an organized attachment set, and condition-specific prep. Ojava cannot and does not: diagnose, prescribe, set a dose, order labs, write a referral, or sign anything. Those are licensed clinical actions. Reports keeps that boundary explicit on the page itself.

What travels with a packet

Each packet carries the evidence behind it: the relevant labs and their trends, the wearable signals, current medications, and the questions you want answered. Sensitive categories follow the same protections as everywhere else in Ojava, withheld by default and included only on an explicit opt-in. For local portable packets, Reports creates a plain-text packet you can copy or export, review, and then share yourself. The emergency card follows that same pattern: local text you control, never automatic sending or a live share. See Exports & sharing for how a finished summary leaves the app, and Privacy for the sensitive-category rules.