Minimum Data Expectations

Populate the following resource types to ensure full chart functionality:

• Patient: Required for all sessions; must include name, identifiers, and demographics
• Encounter: Required to render the timeline view and contextualize clinical events
• DocumentReference: Required to display source documents and enable record provenance
• AllergyIntolerance: For allergies and adverse reactions
• Condition: For problems, diagnoses, and medical history
• MedicationStatement: For documented or reported medications
• Procedure: For surgical history or clinical procedures
• Observation: For vitals, lab results, and test outcomes
• Immunization: For vaccine history
• FamilyMemberHistory: For hereditary conditions
• SocialHistory: For lifestyle and social determinants
• FunctionalStatus: For limitations and abilities
• PlanOfCare: For active care plans and goals
• AdvanceDirectives: For legal care preferences
• Orders and Results: For structured requisitions and diagnostic reports
• ProgressNotes: For authored notes not tied to documents
• Referrals: For inbound or outbound referral information
• ADT Events: For hospital admissions and discharges
• Telephonic Encounters: For documented remote consultations

Test Setup Recommendations

• Include at least one DocumentReference linked to a CCDA, C-CDA on FHIR, or PDF file to enable provenance display.
• Ensure Encounter data is present to allow the chart timeline to render.
• Use a broad mix of resources to simulate realistic longitudinal records.
• Test patients should be enrolled and retrievable via Patient360 to ensure end-to-end coverage.
• Use consistent identifiers and reference chains between resources to avoid validation or launch failures.