Below are some of the high level use cases we expect the patient app to support, along with suggestions on API endpoints that are likely to be useful, known limitations, and potential tips.
While we support some patient permissioned API actions with specially scoped API tokens, this is not widely enough supported to cover the workflows described below. We anticipate that we will support all of these workflows with patient scoped tokens before the conclusion of the contest, so it would be wise to account for this when designing your authentication flow. For now, given that there is no PHI in your team’s EMR, utilize a token that is not restricted to any particular patient.
Sign up for an account and provide basic info
Patient can complete self-registration including entering personal info, insurance coverage, completing necessary consents and questionnaires prior to their initial visit, and a basic medical history.
Canvas cannot store pictures of insurance cards.
Questionnaires can only be completed and submitted once by the patient and do not allow for changes.
3rd party services support card scanning to extract relevant coverage information to reduce potential for manual entry error.
View your medical history
Patient can see their basic medical history information, inclusive of completed forms (consents, questionnaires), appointment history, conditions, medications, immunizations, allergies, imaging & lab results
Canvas messaging does not support threaded messages, but you can retrieve all of a patient’s messages by making two search requests: one where the patient is the sender and another where the patient is the recipient.
Create a “catch all” staff member for messages from the patient to be routed to.
See charges and pay bills
Patient can view their bills and submit a payment for services.