Cortico connects to EMR (Electronic Medical Record) systems in order for most of its' patient engagement systems 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.

Integration Ratings

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.

COMPLETE most complete integration OpenOSP (OpenOscar)
COMPLETE excellent integration

WELL OscarPro (Includes as KAI, THT)

FlowEMR
NEAR COMPLETE excellent integration. minor compatibility issues

Accuro (docs)

Oscar 19

Juno EMR, 
INCOMPLETE missing some small features

 

OpenEMR
LIMITED SUPPORT currently has significant blocker(s) Avaros, MPeer
NO SUPPORT integration not permitted by EMR vendor Indivicare, Epic, Telus EMRs (PS Suite, Med Access, InputHealth, etc)

Known Limitations

Accuro

  • The Cortico plug-in is not yet supported. All other features work fine. We intend to add support via the CDS link system.
  • There are integration fees associated with Accuro

WELL OscarPro

  • There are integration fees associated with WELL OscarPro

Avaros

  • 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)

Oscar (All Versions)

  • Do Not Use the "Availability: Yes/No" field in Oscar S​chedule Setting - S​ome 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.
  • Q​uotes/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>

    O​penOSP: Quotes seem to work fine, and no error is encountered when saving patients.

    W​ELL: Quotes in names seems to work and does not return an error, and apostrophes/single-quotes should not be converted to &apos; in the REST API.

O​scar 19

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:

  • R​EST 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.

Juno

  • 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.