EHR Interfaces Supported by MealSuite Connect
The below EHR systems are supported by the Connect interface. In addition, you will find the message types that are transferred from the EHR system to MealSuite core system.
EHR | Project Tier (see below for definitions and timelines) | Supported Message Types / Integration Details |
American Data | 2 or 3 |
|
Anzer |
2 or 3 |
|
Azalea Health |
2 or 3 |
|
Cerner™ |
2 or 3 |
|
Epic | 2 or 3 |
|
HCS |
2 or 3 |
|
1 |
The interface utilizes the MatrixCare Census Subscriber Feed API to push admission and demographic information in HL7 messages to the MealSuite system when a change is made to a resident. |
|
1 |
The interface utilizes an SFTP connection to send HL7 messages to the MealSuite system when a change is made to a resident. |
|
1 |
The interface utilizes the SOAP API to send HL7 messages to the MealSuite system when a change is made to a resident. |
|
MediPatient |
2 or 3 |
|
Meditech |
2 or 3 |
|
Netsmart myUnity® |
2 or 3 |
|
PointClickCare® | 1 |
The interface utilizes the RESTful API set of the PCC Partner Marketplace platform for real-time synchronization of patient data. Immediately upon a patient being updated in PCC, a webhook notifies MealSuite to trigger a call and retrieve the updated data. Questions Regarding Security? - Because the interface utilizes the PCC proprietary RESTful API set, please consult with your PCC account manager to answer questions related to security, such as the API authentication and authorization method, and traffic encryption levels to protect data. What about PCC QuickMAR?
PCC QuickMAR is not currently supported by the PCC Partner marketplace platform, and as such cannot integrate with MealSuite.
What about PCC American HealthTech (AHT)?
American HealthTech (AHT) was acquired by PCC on January 17, 2024. Until further news of this acquisition transpires, MealSuite has decided not to pursue an integration with AHT.
|
WellSky® | 1 |
The interface utilizes VPN connectivity to send admission and demographic information in HL7 messages to the MealSuite system when a change is made to a resident. |
1 |
The interface utilizes VPN connectivity to send admission and demographic information in HL7 messages to the MealSuite system when a change is made to a resident. |
Project Tier Descriptions and Timelines
The table below describes each project tier and associated timeline when scoping for a MealSuite Connect interface to an EHR.
Tier | Description | Timeline |
1 |
A tier 1 project is a turnkey integration involving a partner EHR. A partner vendor is one with a certified interface that allows for a quicker and easier setup (i.e., "plug and play"), direct access to EHR data, and faster troubleshooting resolution. A turnkey integration does not require development; only client training and data mapping are required. |
Can be completed within three weeks depending on activation on the EHR side and training availability. |
2 |
HL7-based integration for an EHR MealSuite has previously implemented a Connect interface with. A tier 2 project is specific to a site with its own EHR interface that is capable of meeting all or most MealSuite HL7 specifications. |
Can be completed within six weeks depending on availability and scope. |
3 |
HL7-based integration for an EHR MealSuite has previously implemented a Connect interface with, but where MealSuite HL7 specifications are not met and/or multiple parties are involved. For example, the interface is managed by a third-party or shared with other facilities with no possibility of modification. |
Can be completed within nine weeks depending on availability; however longer timelines should be expected if MealSuite HL7 specifications are not met, as this warrants development time on the MealSuite side. |
4 |
A new EHR that MealSuite has not previously implemented a Connect interface with, or an EHR with a non-HL7 based integration. A tier 4 project requires significant development and planning and as such MealSuite will require a technical analysis of feasibility before sending a quote. |
Could be completed in six months depending on complexity and scope. |