Chart Template Builder

Clinician Companion

Chart Template Builder

Use this guided template builder to create a full structured chart JSON payload that can be exported for your own records or imported into Clinician Companion when you have access to the target chart.

Build a Structured Chart JSON Template

Patients and providers can use this public builder to enter structured chart information, generate a complete JSON payload, download it for personal records or migration, and optionally import it directly into Clinician Companion when they already have access to the destination chart.

Subject blockIncluded

Medications1 example row(s)

Statements2 example row(s)

Family history1 example row(s)

Imaging1 example row(s)

How To Use This Builder

Fill out as much chart detail as you have available, including subject demographics, medications, statements, family history, and imaging metadata.
Use Generate JSON Preview to create a structured payload that matches the Clinician Companion importer.
Use Copy JSON or Download JSON if you want a portable export for your own records or another migration workflow.
If you are already signed in to an authorized patient or provider account, use Import Into Clinician Companion to send the generated JSON into an accessible chart.

Subject

Patient + Chart Details

First Name Last Name

Date of Birth Sex

Email Phone

Address

Insurance Name Insurance ID

Status Primary Clinician ID (optional)

Medications

Medication Dosage Instructions Status Notes

Patient Statements

Title Statement

Family Medical History

Relation Condition Notes

Imaging Studies

Study Description Study Date Modality Study Status Visibility Notes

Output

JSON Preview + Export

Generated JSON

{
    "subject": {
        "first_name": "Template",
        "last_name": "Patient",
        "date_of_birth": "2000-01-01",
        "sex": "unknown",
        "status": "active",
        "email": "patient@example.com",
        "phone": "555-555-5555",
        "address": "123 Example Street",
        "insurance_name": "Example Insurance",
        "insurance_id": "ABC123456"
    },
    "patient_statements": [
        {
            "statement_title": "Communication Preferences",
            "statement_text": "Preferred name and pronouns:\n\nPreferred communication style:\n\nAccessibility or sensory needs:\n\nImportant context for visits:"
        },
        {
            "statement_title": "Patient Summary",
            "statement_text": "Primary diagnoses / working diagnoses:\n\nMajor care-team context:\n\nKey risks, triggers, or supports:\n\nGoals for care coordination:"
        }
    ],
    "medications": [
        {
            "medication_name": "Example Medication",
            "dosage": "10 mg",
            "instructions": "Once daily",
            "status": "active",
            "notes": "Replace with the real medication details."
        }
    ],
    "family_history": [
        {
            "relation_label": "Parent",
            "condition_name": "Example Condition",
            "notes": "Replace with real family history details."
        }
    ],
    "imaging_studies": [
        {
            "study_description": "Example Imaging Study",
            "study_date": "2026-01-01",
            "study_status": "received",
            "visibility": "care_team",
            "modality_summary": "MRI",
            "notes": "Optional imaging metadata can be included here for migration intake."
        }
    ]
}

The generated JSON matches the structured import format supported by Clinician Companion. Empty rows are omitted automatically.

Use Inside Clinician Companion

Export-only mode: you can still build, copy, and download a complete chart JSON template from this page, but direct import requires a logged-in patient account or provider access to at least one assigned chart.

Governance + Network

Clinician Companion spans three linked domains with distinct roles for restricted app access, public standards, and supporting tools. Privacy and security features are designed to support regulated workflows, including HIPAA and GDPR-oriented use, but formal compliance also depends on operational and hosting controls beyond plugin code alone.

.appRestricted application and portal access .usPublic information, governance, and standards .toolsTools, workflows, and supporting materials