Data
The data module provides you with data to compute on. It provides curated, secure access to both PHI (e.g. patient data) and non-PHI (e.g. staff and practice-level data), representing the current state of your target Canvas instance. The module’s classes offer convenience methods and operators that make business logic and clinical logic easy to express with standard terminologies like ICD-10, SNOMED-CT, CPT, and the like.
Data module classes are Django ORM models, which allow easy retrieval of data at runtime through Django’s expressive QuerySet API.
The pages below provide listings of the models, their attributes, and examples of usage.
Harmful or undesired physiological responses associated with exposure to a substance.
A scheduled meeting between a patient and a provider.
Teams assigned for patient care.
Structured units of documentation in a patient's chart.
Common choice classes used in multiple models.
Condition, diagnosis, or reason for seeking medical attention.
Patient insurance coverage.
Actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient.
Type of a manufactured item that is used in the provision of healthcare.
Analysis of imaging tests to obtain information about the health of a patient.
Analysis of clinical specimens to obtain information about the health of a patient.
Lab partners and the tests they offer within Canvas.
Clinical notes on patient charts.
Measurements and simple assertions made about a patient.
The clinical organization present in the Canvas EMR.
Data used to categorize individuals for identification, records matching, and other purposes.
The practice locations present in the Canvas EMR.
A record of a protocol being snoozed for a patient.
Groups of coded questions and the coded patient responses.
The reason for a patient's visit.
Data associated with Staff members.
Data associated with Tasks.
Data associated with Teams.
Lists of codes and terms from various clinical coding systems grouped by a defining concept.