What telemedicine for a critical access hospital needs to do
A critical access hospital or small rural hospital usually has nurses and generalist physicians on site but no cardiologist, neurologist or infectious disease specialist down the hall. Telemedicine for critical access hospitals closes that gap by bringing the specialist to the patient by video. The video call alone is not enough, though: the specialist needs to hear the heart and lungs, read a 12-lead ECG, see vital signs as they change and look into an ear or at a wound. That is the job of the connected devices and of the trained person who operates them.
MedConnect is a telemedicine station and software built by Promotal (Groupe ELOI) and assembled and configured in Ernée, France. It is deployed in France and six other countries, including the United States, where a customer uses it for at-home consultations in partnership with clinics. The model is always the same: a nurse or other on-site assistant presents the patient while the remote physician consults by secure video and sees every measurement live—see assisted teleconsultation for the full nurse-presented workflow.
The specialty-consult workflow, step by step
Before the consult
- 1. The attending physician requests a specialty consult under your hospital’s protocol.
- 2. The consult is scheduled or placed in the virtual waiting room, where the specialist sees the queue.
- 3. The telepresenter opens the patient record, confirms identity and records consent.
During and after
- 4. Secure video opens with two streams: the patient’s face and the live device feed.
- 5. The specialist directs the exam; vitals, auscultation, camera images and the ECG arrive in real time.
- 6. The specialist documents a recommendation; data and reports are stored with the consultation and can be sent to your EHR.
Not every consult has to be live. For non-urgent questions—a wound photo, an ECG review, a follow-up after discharge—the team can collect the exam data and send it as a store-and-forward (asynchronous) case for the specialist to review later. Several clinicians can also join one session when a case needs more than one opinion.
Configuration options: cart, station or kit
The right form factor depends on where your patients are when they need the specialist. All three run the same software and device set, so a hospital can start with one and add another later. For a side-by-side view of the two most common choices, read telehealth kit vs telehealth cart.
| Setting | Best configuration | Why |
| Emergency department and inpatient bedside | Telehealth cart | Rolls to the patient, keeps devices charged and mounted, ready for unplanned consults |
| Outpatient specialty clinic room | Fixed station / nurse-led telehealth center | A dedicated room for scheduled specialty days (cardiology, endocrinology, behavioral health) |
| Swing beds, outreach clinics and home follow-up | Portable telehealth kit | Travels in a case to wherever the nurse sees the patient; a backpack version suits home visits |
Telehealth cart for rural hospitals: device set by use case
The US basic configuration uses FDA-cleared and FDA-registered devices. Clearance status below was checked against FDA records; component documentation is available on request.
| Use case | Device | What the specialist gets | FDA status |
| General exam | Edan iM3s vital signs monitor | Blood pressure, SpO2, pulse and temperature displayed live | FDA-cleared, 510(k) K202892 / K233038 |
| General exam | Riester ri-sonic USB electronic stethoscope | Heart, lung and abdominal sounds streamed to the remote clinician | FDA-cleared, 510(k) K132560 |
| General exam | Firefly digital otoscope and Firefly exam camera | Live ear, throat, skin and wound images on the second video stream | Class I, 510(k)-exempt, FDA-registered |
| Cardiology | Edan SE-1515 12-lead PC ECG (DX12 wireless / DP12 USB) | 12-lead ECG launched from the consult screen; the PDF report attaches to the consultation automatically (GDT) | FDA class II, 510(k) K152427 |
Other devices can be added for specific service lines; see the full telehealth equipment range. We confirm the clearance status of any added device for your configuration rather than describing the whole catalog as FDA-cleared.
How it works with your existing EHR and billing
MedConnect does not replace your EHR and does not do billing or claims. Your hospital keeps its own systems; MedConnect connects to them. The telehealth platform supports HL7, FHIR R4 (for vital signs, via AIView), GDT for ECG devices, BLE and USB for devices, and a REST API for server-to-server exchange of patient, staff and exam data. The interface scope is defined with your IT team during solution design.
Coverage and payment rules for telehealth differ by payer, state and service, and they change. Your organization is responsible for validating them. Neutral starting points include the Center for Connected Health Policy and telehealth.hhs.gov.
Data security
- HIPAA-ready, and we sign a Business Associate Agreement (BAA).
- US customer data hosted on AWS in the United States (us-east-1).
- Video consultations end-to-end encrypted (AWS Chime SDK).
- ISO 27001:2022 certified information security management, certified by the British Assessment Bureau.
- Role-based access, multi-factor authentication and enterprise single sign-on (SAML / OIDC).
More detail is on our telehealth compliance page.
Deployment and support
We are direct about how delivery works. We assemble and configure the equipment, ship it directly to your hospital, train your team remotely by video and provide remote support afterwards. We do not have a US distributor or an on-site installation team. Because each cart, station or kit arrives configured and tested, setup on your side is mostly connecting it to your network and accounts. Training covers the telepresenter role—US resources such as the regional Telehealth Resource Centers also offer telepresenter training.
Funding the equipment
Many rural hospitals fund telehealth equipment through grants rather than operating budgets. The Rural Health Transformation Program sends funding to states, which re-grant it to providers; some state programs list telehealth equipment and exam devices as eligible supplies. Our Rural Health Transformation Program telehealth guide explains how that money flows to equipment buyers. Other federal sources include the USDA Distance Learning and Telemedicine grants and the FCC Rural Health Care Program, which supports connectivity for eligible rural health care providers. Each program sets its own eligibility and rules; check the current notice with the administering agency.
What to ask any telehealth vendor
- Which devices are FDA-cleared, which are FDA-registered, and can you document it per device?
- Does the specialist see device data live, or only after the call?
- Do you support both live and store-and-forward consults?
- Will you sign a BAA, and where is US patient data hosted?
- Which interfaces do you support to our EHR (HL7, FHIR, API)?
- Who installs, trains and supports us—on site or remotely—and what are the support hours?
- Do you provide physicians, or do we bring our own network?
- Can you supply component documentation for grant compliance reviews?
What MedConnect does not do
- No specialist staffing. We do not employ or provide physicians. You bring your own medical staff, a partner health system or a contracted specialist network.
- No billing or claims. Your billing system and team stay in charge.
- No on-site installation. Equipment ships configured; training and support are remote.
Running a rural health clinic or FQHC rather than a hospital? See telehealth for rural health clinics and FQHCs. For post-discharge visits at home, see home health telehealth and remote patient monitoring. Evaluating other vendors? Read GlobalMed alternatives.