MESI mCONNECT Services catalogue
1 Introduction
This document provides a detailed specification of our off-the-shelf connectivity services. It is designed to give our customers a clear understanding of the features and capabilities included in each connectivity package. This document can be referenced in contracts and Statements of Work (SOWs) to ensure alignment on project scope and deliverables.
Each connectivity service listed below has a detailed specification section that outlines the Minimum Viable Product (MVP) features, technical requirements, and other important details.
2 Software updates and maintenance
For cloud-based deployments, software updates, enhancements, and security patches are deployed automatically by Connectivity team. Customers are notified at least seven (7) days in advance of any scheduled updates that may impact service availability or functionality.
For on-premises deployments, customers are notified of available updates. Upon customer request, the installer or software package is provided to the customer for deployment within their environment. Installation and upgrade execution are performed by the customer unless otherwise agreed in writing.
3 Available connectivity packages
Below is a table-like view of our currently available off-the-shelf connectivity packages:
| EHR system | Data format | Deployment model |
|---|---|---|
| Best Practice | JSON | Cloud (SaaS) |
| Birpis | HL7 | On-premise |
| Doctolib | GDT | On-premise |
| Hipokrat | HL7 | On-premise |
| Iris | HL7 | On-premise |
| Isoz | HL7 | On-premise |
| Join | JSON | Cloud (SaaS) |
| NextGen | HL7 | On-premise |
| Tomedo | GDT | Out of device |
| Vena | JSON | Cloud (SaaS) |
| Webdoc | JSON | Cloud (SaaS) |
| WEDA | HL7 | On-premise |
| ZipLaneRx | JSON | Cloud (SaaS) |
3.1 Best Practice
This service delivers a ready‑made, cloud‑hosted integration between Best Practice EHR system and MESI mCONNECT API thru HALO Connect. It is built on Azure as an “Integration API” component and is designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.1.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | HTTPS |
| Interaction method / protocol | REST-based API |
| Integration pattern | Synchronous, asynchronous |
| Data format | JSON in SQL Passthrough |
| Authorization | API key |
3.1.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Patient demographics | Patient ID, name, surname, date of birth, gender, status. |
| Measurement payload exchange | MESI sends processed results in predefined JSON structure to HALO endpoint (async method). |
| Device configuration and status | Cloud Dashboard access to delete appointments from the Dashboard, resend measurements (pooling mechanism) and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | API key. |
3.1.3 Data flow
Scheduling appointments and transferring patient data: MESI Integration API requests appointments on each mTABLET invocation.
Sending measurement results: MESI sends a POST request towards HALO endpoint.
3.2 Birpis
This service delivers a ready‑made, on-premise hosted integration between Birpis EHR system and MESI connectivity software. It is built on NextGen’s Mirth Connect platform and designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.2.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | TCP |
| Interaction method / protocol | Message |
| Integration pattern | Synchronous |
| Data format | HL7 |
| Authorization | IP whitelisting |
3.2.2. MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Message metadata | Message timestamp (MSH.7.1) used for request date processing. |
| Patient identification | Patient ID and full patient name (PID-3, PID-5), including structured name components. |
| Patient demographics | Date of birth, administrative sex (mapped), race (including internal race_code mapping), and primary language. |
| Patient contact information | Address (street, city, postal code, country, address type), phone number, and email. |
| Encounter / visit information | Patient class, location, admission type, visit number (with assigning authority and type), visit timestamps. |
| Provider information | Attending provider (PV1-7) and ordering provider (ORC-12, OBR-16). |
| Order management | Order control, placer/filler order numbers, group number, order status, response flag, timing/quantity/priority, transaction timestamp, effective date. |
| Observation / procedure request | Universal service ID, priority, requested/scheduled/observation timestamps, diagnostic section, timing block (OBR-27), technician info, procedure code. |
| Measurement payload exchange | Connectivity software sends an outbound ORU R01 message to user defined EHR IP and port specification. ORU R01 contains both raw measurement data in MESI predetermined HL7 structure along with Base64 encoded PDF. |
| Device configuration and status | Locally deployed Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | N/A |
3.2.3 Data flow
Scheduling appointments and transferring patient data: EHR sends ORM O01 order request to connectivity software via TCP.
Sending measurement results: Connectivity software creates a ORU R01 measurement request and sends it towards EHR IP and port configuration.
3.3 Doctolib
This service delivers two ready‑made integrations:
MESI mTABLET and Doctolib using the Worklist Direct application found on mTABLET device.
MESI on-premise hosted integration supporting GDT data format. It is MESI custom built software designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.3.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | FTP |
| Interaction method / protocol | File transfer |
| Integration pattern | Asynchronous |
| Data format | GDT |
| Authorization | N/A (infrastructure defined) |
3.3.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| System / partner identification | Sender/receiver identifiers and labels are present with additional system codes/IDs. |
| GDT message metadata | Technical fields that describe the message format/version/record type are present (e.g., “8000”, “8100”, “9206”, “9218”, “8402”, “8609”). |
| Patient demographics | Patient first name (3101), last name (3102), date of birth (3103), and sex/gender (3110). |
| Patient identifiers | A patient-specific identifier (3105). |
| Patient address | Postal code (3112), city (3113), plus additional address lines (3106, 3107). |
| Patient contact | Email address (3633). |
| Order / service request | The requested service/test (2998). |
| Order / request identifiers | A request/order reference (2999), along with additional order-related numeric identifiers (3626, 3629). |
| Measurement payload exchange | Connectivity software drops a measurement GDT and PDF file to a user defined folder. |
| Device configuration and status | Locally deployed Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | N/A |
3.3.3 Data flow
Scheduling appointments and transferring patient data: Doctolib drops a GDT file in user defined inbound folder that the software validates and processes.
Sending measurement results: Connectivity software creates a measurement GDT and PDF file in the user defined outbound folders.
3.4 Hipokrat
This service delivers a ready‑made, on-premise hosted integration between Hipokrat EHR system and MESI connectivity software. It is built on NextGen’s Mirth Connect platform and designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.4.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | TCP |
| Interaction method / protocol | Message |
| Integration pattern | Synchronous |
| Data format | HL7 |
| Authorization | IP whitelisting |
3.4.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Message metadata | Message timestamp (MSH.7.1) used for request date processing. |
| Patient identification | Patient ID and structured patient name (PID-3, PID-5). |
| Patient demographics | Date of birth, administrative sex (mapped), race (including internal race_code mapping), and primary language. |
| Patient contact information | Address details (PID-11), phone and email (PID-13). |
| Encounter / visit information | Patient class, assigned location, admission type, visit number (with assigning authority and type), visit timestamps (PV1 segment). |
| Provider information | Attending provider (PV1-7), ordering provider (ORC-12), and OBR ordering provider (OBR-16). |
| Order management | Order control, placer/filler identifiers, group number, order status, response flag, timing/quantity/priority details, transaction timestamp, effective date (ORC segment). |
| Observation / procedure request | Universal service ID (e.g., ECG), priority, requested/observation/scheduled timestamps, diagnostic service section, timing block (OBR-27), technician information, procedure code (OBR segment). |
| Measurement payload exchange | Connectivity software sends an outbound ORU R01 message to user defined EHR IP and port specification. ORU R01 contains both raw measurement data in MESI predetermined HL7 structure along with Base64 encoded PDF. |
| Device configuration and status | Locally deployed Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | N/A |
3.4.3 Data flow
Scheduling appointments and transferring patient data: EHR sends ORM O01 order request to connectivity software via TCP.
Sending measurement results: Connectivity software creates a ORU R01 measurement request and sends it towards EHR IP and port configuration.
3.5 Iris
This service delivers a ready‑made, on-premise hosted integration between Iris EHR system and MESI connectivity software. It is built on NextGen’s Mirth Connect platform and designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.5.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | TCP |
| Interaction method / protocol | Message |
| Integration pattern | Synchronous |
| Data format | HL7 |
| Authorization | IP whitelisting |
3.5.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Message metadata | Message timestamp (MSH.7.1) used for request date processing. |
| Patient identification | Patient ID and structured patient name (PID-3, PID-5). |
| Patient demographics | Date of birth, administrative sex (mapped), race (including internal race_code mapping), and primary language. |
| Patient contact information | Address details (PID-11), phone and email (PID-13). |
| Encounter / visit information | Patient class, assigned location, admission type, visit number (with assigning authority and type), visit timestamps (PV1 segment). |
| Provider information | Attending provider (PV1-7), ordering provider (ORC-12), and OBR ordering provider (OBR-16). |
| Order management | Order control, placer/filler identifiers, group number, order status, response flag, timing/quantity/priority details, transaction timestamp, effective date (ORC segment). |
| Observation / procedure request | Universal service ID (e.g., ECG), priority, requested/observation/scheduled timestamps, diagnostic service section, timing block (OBR-27), technician information, procedure code (OBR segment). |
| Measurement payload exchange | Connectivity software sends an outbound ORU R01 message to user defined EHR IP and port specification. ORU R01 contains both raw measurement data in MESI predetermined HL7 structure along with Base64 encoded PDF. |
| Device configuration and status | Locally deployed Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | N/A |
3.5.3 Data flow
Scheduling appointments and transferring patient data: EHR sends ORM O01 order request to connectivity software via TCP.
Sending measurement results: Connectivity software creates a ORU R01 measurement request and sends it towards EHR IP and port configuration.
3.6 Isoz
This service delivers a ready‑made, on-premise hosted integration between Isoz EHR system and MESI connectivity software. It is built on NextGen’s Mirth Connect platform and designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.6.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | TCP |
| Interaction method / protocol | Message |
| Integration pattern | Synchronous |
| Data format | HL7 |
| Authorization | IP whitelisting |
3.6.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Message metadata | Message timestamp (MSH.7.1) used for request date processing. |
| Patient identification | Patient ID and structured patient name (PID-3, PID-5). |
| Patient demographics | Date of birth, administrative sex (mapped), race (including internal race_code mapping), and primary language. |
| Patient contact information | Address details (PID-11), phone and email (PID-13). |
| Encounter / visit information | Patient class, assigned location, admission type, visit number (with assigning authority and type), visit timestamps (PV1 segment). |
| Provider information | Attending provider (PV1-7), ordering provider (ORC-12), and OBR ordering provider (OBR-16). |
| Order management | Order control, placer/filler identifiers, group number, order status, response flag, timing/quantity/priority details, transaction timestamp, effective date (ORC segment). |
| Observation / procedure request | Universal service ID (e.g., ECG), priority, requested/observation/scheduled timestamps, diagnostic service section, timing block (OBR-27), technician information, procedure code (OBR segment). |
| Measurement payload exchange | Connectivity software sends an outbound ORU R01 message to user defined EHR IP and port specification. ORU R01 contains both raw measurement data in MESI predetermined HL7 structure along with Base64 encoded PDF. |
| Device configuration and status | Locally deployed Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | N/A |
3.6.3 Data flow
Scheduling appointments and transferring patient data: EHR sends ORM O01 order request to connectivity software via TCP.
Sending measurement results: Connectivity software creates a ORU R01 measurement request and sends it towards EHR IP and port configuration.
3.7 Join
This service delivers a ready‑made, cloud‑hosted integration between Join EHR system and MESI mCONNECT API. It is built on Azure as an “Integration API” component and is designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.7.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | HTTPS |
| Interaction method / protocol | REST-based API |
| Integration pattern | Synchronous |
| Data format | JSON |
| Authorization | OAuth 2.0 |
3.7.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Patient demographics | Sync of patient ID, name, DOB, gender, visit unique identifiers, tablet group and measurement that needs to be performed on the patient. |
| Measurement payload exchange | MESI sends processed results in predefined JSON structure to Join endpoint. |
| Device configuration and status | Cloud Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | OAuth 2.0 bearer token exchange. |
3.7.3 Data flow
Scheduling appointments and transferring patient data: Join sends a POST request towards MESI Integration API.
Sending measurement results: MESI sends a POST request towards Join endpoint.
3.8 NextGen
This service delivers a ready‑made, on-premise hosted integration between NextGen EHR system and MESI connectivity software. It is built on NextGen’s Mirth Connect platform and designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.8.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | TCP |
| Interaction method / protocol | Message |
| Integration pattern | Synchronous |
| Data format | HL7 |
| Authorization | IP whitelisting |
3.8.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Message metadata | Message timestamp (MSH.7.1) used for request date processing. |
| Patient identification | Patient ID and structured patient name (PID-3, PID-5). |
| Patient demographics | Date of birth, administrative sex (mapped), race (including internal race_code mapping), and primary language. |
| Patient contact information | Address details (PID-11), phone and email (PID-13). |
| Encounter / visit information | Patient class, assigned location, admission type, visit number (with assigning authority and type), visit timestamps (PV1 segment). |
| Provider information | Attending provider (PV1-7), ordering provider (ORC-12), and OBR ordering provider (OBR-16). |
| Order management | Order control, placer/filler identifiers, group number, order status, response flag, timing/quantity/priority details, transaction timestamp, effective date (ORC segment). |
| Observation / procedure request | Universal service ID (e.g., ECG), priority, requested/observation/scheduled timestamps, diagnostic service section, timing block (OBR-27), technician information, procedure code (OBR segment). |
| Measurement payload exchange | Connectivity software sends an outbound ORU R01 message to user defined EHR IP and port specification. ORU R01 contains both raw measurement data in MESI predetermined HL7 structure along with Base64 encoded PDF. |
| Device configuration and status | Locally deployed Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | N/A |
3.8.3 Data flow
Scheduling appointments and transferring patient data: EHR sends ORM O01 order request to connectivity software via TCP.
Sending measurement results: Connectivity software creates a ORU R01 measurement request and sends it towards EHR IP and port configuration.
3.9 Tomedo
This service delivers two ready‑made integrations:
MESI mTABLET and Tomedo using the Worklist Direct application found on mTABLET device.
MESI on-premise hosted integration supporting GDT data format. It is MESI custom built software designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.9.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | FTP |
| Interaction method / protocol | File transfer |
| Integration pattern | Asynchronous |
| Data format | GDT |
| Authorization | N/A (infrastructure defined) |
3.9.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| System / partner identification | Sender/receiver identifiers and labels are present with additional system codes/IDs. |
| GDT message metadata | Technical fields that describe the message format/version/record type are present (e.g., “8000”, “8100”, “9206”, “9218”, “8402”, “8609”). |
| Patient demographics | Patient first name (3101), last name (3102), date of birth (3103), and sex/gender (3110). |
| Patient identifiers | A patient-specific identifier (3105). |
| Patient address | Postal code (3112), city (3113), plus additional address lines (3106, 3107). |
| Patient contact | Email address (3633). |
| Order / service request | The requested service/test (2998). |
| Order / request identifiers | A request/order reference (2999), along with additional order-related numeric identifiers (3626, 3629). |
| Measurement payload exchange | Connectivity software drops a measurement GDT and PDF file to a user defined folder. |
| Device configuration and status | Locally deployed Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | N/A |
3.9.3 Data flow
Scheduling appointments and transferring patient data: Tomedo drops a GDT file in user defined inbound folder that the software validates and processes.
Sending measurement results: Connectivity software creates a measurement GDT and PDF file in the user defined outbound folders.
3.10 Vena
This service delivers a ready‑made, cloud‑hosted integration between Vena EHR system and MESI mCONNECT API thru Leyr platform. It is built on Azure as an “Integration API” component and is designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.10.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | HTTPS |
| Interaction method / protocol | REST-based API |
| Integration pattern | Synchronous |
| Data format | JSON |
| Authorization | Client ID/secret |
3.10.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Patient demographics | Patient ID, name, surname, date of birth, address information, practitioner name/surname, gender, visit unique identifiers, tablet group and measurement that needs to be performed on the patient. |
| Measurement payload exchange | MESI sends processed results in predefined JSON structure to Leyr endpoint. |
| Device configuration and status | Cloud Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | Client ID/secret. |
3.10.3 Data flow
Scheduling appointments and transferring patient data: MESI Integration API requests appointments on each mTABLET invocation.
Sending measurement results: MESI sends a POST request towards Leyr endpoint.
3.11 Webdoc
This service delivers a ready‑made, cloud‑hosted integration between Webdoc EHR system and MESI mCONNECT API thru Leyr platform. It is built on Azure as an “Integration API” component and is designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.11.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | HTTPS |
| Interaction method / protocol | REST-based API |
| Integration pattern | Synchronous |
| Data format | JSON |
| Authorization | Client ID/secret |
3.11.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Patient demographics | Patient ID, name, surname, date of birth, address information, practitioner name/surname, gender, visit unique identifiers, tablet group and measurement that needs to be performed on the patient. |
| Measurement payload exchange | MESI sends processed results in predefined JSON structure to Leyr endpoint. |
| Device configuration and status | Cloud Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | Client ID/secret. |
3.11.3 Data flow
Scheduling appointments and transferring patient data: MESI Integration API requests appointments on each mTABLET invocation.
Sending measurement results: MESI sends a POST request towards Leyr endpoint.
3.12 WEDA
This service delivers a ready‑made, on-premise hosted integration between WEDA EHR system and MESI connectivity software. It is built on NextGen’s Mirth Connect platform and designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.12.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | HTTP, FTP |
| Interaction method / protocol | REST-based API, file transfer |
| Integration pattern | Synchronous, asynchronous |
| Data format | HL7 |
| Authorization | Token based |
3.12.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Patient demographics | Supports patient ID (PID-3.1), name (PID-5.), DOB (PID-7.1), sex/gender mapping from PID-8.1 and race (PID-10.* with internal race_code mapping). |
| Patient contact information | Supports address (PID-11[0].1/.3/.5/.6/.7), phone (PID-13[0].1/.2/.3), and email (PID-13[0].4). |
| Encounter / visit information | Supports visit details from PV1 including patient class (PV1-2.1), location (PV1-3.1), admission type (PV1-4.1), service (PV1-10.1), visit number (PV1-19.*), admit/discharge date-times (PV1-44.1, PV1-45.1). |
| Provider information | Supports attending doctor (PV1-7.), ordering provider at ORC level (ORC-12.) and OBR level (OBR-16.*). |
| Order management | Supports order control and identifiers, status, timing, entered/verified by, callback phone, and effective date-time from ORC. |
| Observation / procedure request | Supports service/procedure info, requested/scheduled times, diagnostic section, technician data, and timing blocks from OBR. |
| Message metadata | Uses MSH-7.1 as request timestamp; also stamps a current “requestedDate”; derives task_type/activity_id from ORC-2.1. |
| Measurement payload exchange | MESI sends processed results in predefined HL7 structure to WEDA endpoint. |
| Device configuration and status | Locally deployed Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | API token use. |
3.12.3 Data flow
Scheduling appointments and transferring patient data: WEDA drops a HL7 file in predetermined inbound folder that MESI connectivity solution validates and processes.
Sending measurement results: MESI sends a POST request towards WEDA endpoint.
3.13 ZipLaneRx
This service delivers a ready‑made, cloud‑hosted integration between ZipLaneRx EHR system and MESI mCONNECT API. It is built on Azure as an “Integration API” component and is designed to provide secure, bidirectional data exchange for patient demographics, measurement payloads and device configuration.
3.13.1 Service overview
| EHR element | Description |
|---|---|
| Transport layer | HTTPS |
| Interaction method / protocol | REST-based API |
| Integration pattern | Synchronous |
| Data format | JSON |
| Authorization | OAuth 2.0 bearer token exchange, client ID/secret |
3.13.2 MVP features included
The Minimum Viable Product (MVP) focuses on the core data flows required by most clinics to onboard patients and ingest measurement results.
| Feature category | Description |
|---|---|
| Patient demographics | Sync of patient ID, name, DOB, gender, visit unique identifiers, tablet group and measurement that needs to be performed on the patient. |
| Measurement payload exchange | MESI sends processed results in predefined JSON structure to ZipLaneRx endpoint. |
| Device configuration and status | Cloud Dashboard access to delete appointments from the Dashboard and manage mTABLET devices and corresponding tablet groups. |
| Authorization framework | Token based, client ID/secret. |
3.13.3 Data flow
Scheduling appointments and transferring patient data: ZipLaneRx sends a POST request towards MESI Integration API.
Sending measurement results: MESI sends a POST request towards ZipLaneRx endpoint.
4 Plan duration and payments
· mConnect Direct, API, and API+ term starts on the date of signature of the Agreement.
· mConnect Custom term starts once the end user officially signs off the completion of the integration project.
