Circle V2 API Docs
    Preparing search index...

    Variable CHART_DOCUMENT_TAGSConst

    CHART_DOCUMENT_TAGS: readonly [
        "biopsychosocial",
        "asam_assessment",
        "level_of_care_determination",
        "history_and_physical",
        "psychiatric_evaluation",
        "nursing_intake",
        "screening_instrument",
        "alcohol_withdrawal_assessment",
        "benzodiazepine_withdrawal_assessment",
        "opioid_withdrawal_assessment",
        "treatment_plan",
        "safety_plan",
        "continuing_care_plan",
        "progress_note",
        "group_note",
        "individual_therapy_note",
        "family_session_note",
        "case_management_note",
        "restraint_seclusion",
        "consent_form",
        "diagnosis",
        "admission",
        "discharge_summary",
        "discharge_instructions",
        "transfer_note",
        "program_history",
        "appointment",
        "insurance",
        "utilization_review",
        "vital_signs",
        "lab_result",
        "glucose_log",
        "clinical_orders",
        "medication_administration_record",
        "medication_reconciliation",
        "other",
    ] = ...

    Our own vocabulary for what a patient chart is, independent of which EMR produced it.

    EMRs don't always have specific types or tables for different document types, so this standardizes them for us. It is a plain Zod vocabulary rather than a pgEnum: a chart carries a set of these, because real documents combine forms (a BPS with an ASAM multidimensional assessment appended) and because a single label cannot say both what a document is and what it substantively contains. Adding or renaming a tag is therefore a code change and a reclassification, never a migration.