Cortico Features
List of integration support & limitations, between Cortico and specific EMRs
Updated 13 hours ago
Cortico connects to EMR (Electronic Medical Record) systems in order for many of its' patient engagement tools to operate and automate administrative work at Medical Practices. Different EMRs have different levels of integration with Cortico. We discuss what's involved in the EMR integration here.
Note if you do not see your EMR below, please speak with us! We regularly add new integrations when there is demand for them!
The following ratings are based purely on how complete and cost-effective the Cortico integration is with each EMR below. Limitations are often due to finite developer resource on the side of Cortico or the EMR Vendor.
includes KAI & THT
contact help@cortico.health to be queued up for onboarding as soon as the integration is ready!
under feasibility evaluation and/or awaiting development resources. contact help@cortico.health to be added to the waitlist or if you want to be a champion clinic!
needs stronger business case to commit to feasibility study. contact help@cortico.health to be added to the waitlist or if you want to be a champion clinic!
vendor may have blocked permit integration. may be business and/or technical blocker(s). contact help@cortico.health if interested in being a champion clinic!
**Avaros has discontinued support for Cortico. We hope they may restore the connection in the future, so please be sure to let them know if you'd like to use Cortico!
The plugin automations such as eligiblity check automation only work in web based EMRs.
Only files in the Documents and Generated Letters folders in the patient chart (and custom files) can be attached and directly in our patient messaging system. Other files, such as Clinical Notes, Forms, and Labs can be downloaded to Citrix and sent through the Cortico messenger as a custom file attachment.
There are integration fees associated with WELL OscarPro
New Avaros installs of any Cortico products are currently blocked because the latest version does not support the Oscar Schedule API. Existing Cortico users are using an older version of Avaros, and are not affected currently. Avaros has indicated intent to develop the schedule API in their new version (no timeline specified as of 2022-07-26)
Specialist Roster date automation is an Oscar-only tool.
Do Not Use the "Availability: Yes/No" field in Oscar Schedule Setting - Some clinics use "Availability: Yes/No" in the Oscar Schedule Setting field. This field doesn't seem to work in the Oscar schedule API (the schedule timeslots are still included when Availability is set to "No"). They should remove the schedule from that date instead of setting Availability: No, or use Do not book blocks.
Oscar Reserved Appointment Status Codes - The "C" (Cancelled) and "D" (Deleted) Appointment Status Codes have special behaviour within Oscar that affect the appointment APIs. Clinics should not move or overwrite these statuses, and Cortico should use the original "C" Cancelled status.
Quotes/apostrophes (e.g. O'Neil) in patient names - Juno returns the following error when trying to create or save patients with apostrophes in fields such as the patient's name:
ERROR 2022-07-12 09:34:03,554 <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>No html tags and no quotes, line breaks or semicolons are allowed.</faultstring><detail><ns1:Exception xmlns:ns1="http://v1.soap.external.ws.oscarehr.org/"/></detail></soap:Fault></soap:Body></soap:Envelope>OpenOSP: Quotes seem to work fine, and no error is encountered when saving patients.
WELL: Quotes in names seems to work and does not return an error, and apostrophes/single-quotes should not be converted to ' in the REST API.
Oscar 19 is a new integration which has some known issues as well as unknown behaviour that may result in Cortico features not working. Known issues include:
REST API may not work due to inconsistent proxy setups. We do not officially support using the REST API with Oscar 19. This means new patients may not be registered and patients may not be updated.
PHN validation - Some Juno instances have validation to prevent adding patients with invalid PHNs (e.g. 1234512345) directly in the EMR, through the API, or both. This may prevent registering test patients
File Upload to the EMR is unsupported in the EMR.
Myle is a partial integration, supporting only the Kiosk and Health System aggregated digital front door functionality. Contact us if you need additional features as they can likely be made available.
Appointment confirmations and other appointment updates (Kiosk "Here" status) are not available.
Attaching files to patient messages is manual (no automatic loading from EMR)
The plugin automations such as eligiblity check automation only work in web based EMRs