Rural health clinics · FQHCs · community health centers
Telehealth for Rural Health Clinics and FQHCs, with Connected Exam Devices
The most effective rural health clinic telehealth setup is a nurse-presented visit: a nurse or medical assistant examines the patient with connected devices—vital signs monitor, electronic stethoscope, 12-lead ECG, otoscope—while a remote physician directs the exam over secure video and sees every measurement live. MedConnect delivers that workflow for RHCs, FQHCs and community health centers as a fixed station, cart or portable kit, with FDA-cleared and FDA-registered devices.
The short answer for medical directors
For a rural health clinic, FQHC or community health center, the telehealth setup that adds the most clinical value is not a webcam visit—it is a telepresenter-led exam with connected diagnostic devices. The on-site nurse handles the hands-on part of the exam; the remote physician or specialist hears the heart and lungs through the electronic stethoscope, reads the ECG, sees the eardrum or skin through the exam camera and watches blood pressure and SpO2 update in real time. That turns a video call into an examination the remote clinician can document.
MedConnect is a telemedicine station and software built by Promotal (Groupe ELOI), assembled and configured in Ernée, France, and deployed in France and six other countries, including the United States, where a customer uses it for at-home consultations in partnership with clinics.
How a nurse-presented visit works
- Intake: the telepresenter identifies the patient, records the reason for the visit and confirms consent according to your clinic’s policy.
- Connect: the patient enters the virtual waiting room; the remote physician sees the queue and opens the session.
- Examine: two video streams run at once—the patient’s face and the live device feed. The physician directs the nurse: auscultation, otoscopy, skin images, vital signs.
- Capture: a 12-lead ECG is launched from the consultation; the PDF report is attached to the record automatically.
- Close: the physician documents the assessment and next steps; the record flows to your EHR through the agreed interface.
When a live session is not practical—limited physician hours, time zones, weak bandwidth—the same devices support a store-and-forward visit: the nurse collects the exam data and a physician reviews it later. The full workflow is described on the assisted teleconsultation page.
Share scarce physician and specialist time across sites
Many RHCs and FQHCs run several small sites with limited on-site physician hours. A hub-and-spoke model lets each spoke site keep a trained telepresenter and a MedConnect station, while the physicians and specialists your organization already works with join from the hub or from home. The platform supports this with a virtual waiting room that shows queued patients in real time, multi-practitioner scheduling across establishments, and multi-site administration so an operations lead can see consultation activity across every location. The clinical staffing model—who covers which site, and when—remains your organization’s decision.
Choose the configuration for each site
| Setting | Best format | Why |
|---|---|---|
| Dedicated exam room at a clinic site | Fixed station / nurse-led telehealth center | Always set up, fastest to start a session, devices mounted and charged in one place |
| Shared between rooms or departments | Telehealth cart | Rolls to the patient; one unit serves several exam rooms |
| Outreach, school-based and home visits | Portable telehealth kit | Carried by a nurse or community health worker to wherever the patient is |
| Mobile teams on foot or in vehicles | Telehealth backpack | Lightest format for field work |
Most multi-site organizations mix formats: stations at the busiest sites, a kit for outreach. See kit vs cart for the trade-offs, and the full telehealth equipment range.
Connected devices and FDA status
The US basic kit is built from FDA-cleared and FDA-registered devices. Status below was checked against FDA’s public database; component documentation is available on request.
| Device | Use in the visit | FDA status |
|---|---|---|
| Edan iM3s vital signs monitor | Blood pressure, SpO2 and pulse, shown live to the physician | FDA-cleared, 510(k) K202892 / K233038 |
| Edan SE-1515 12-lead PC ECG (DX12 wireless / DP12 USB) | Resting 12-lead ECG; PDF report attached automatically | FDA Class II, 510(k) K152427 |
| Riester ri-sonic USB electronic stethoscope | Heart and lung sounds streamed to the remote physician | FDA-cleared, 510(k) K132560 |
| Firefly digital otoscope | Ear and throat images | FDA Class I, 510(k)-exempt, FDA-registered |
| Firefly general exam camera | Skin, wound and general exam images | FDA Class I, 510(k)-exempt, FDA-registered |
The telepresenter: role and training
In US telehealth, the telepresenter is the on-site person—often an RN, LPN or medical assistant—who prepares the patient, operates the devices and acts as the remote physician’s hands. Scope of practice depends on the credential and the state, so your clinic defines who can present and what they may do. We train your telepresenters remotely on the equipment and software. For neutral, vendor-independent competency training, regional Telehealth Resource Centers publish materials, including the Great Plains Telehealth Resource and Assistance Center (GPTRAC) and South Central Area Health Education Center (SCAHEC), which offers a telepresenter certification.
Billing and policy: what MedConnect does and does not do
MedConnect does not do billing or claims, and makes no reimbursement claims. Your organization keeps its own EHR and practice-management or billing software; MedConnect connects to it. Medicare, Medicaid and commercial rules for RHCs and FQHCs acting as originating or distant sites vary by payer and state and have changed repeatedly in recent years. Your organization is responsible for validating current rules before launching a service. Neutral, regularly updated sources:
- Center for Connected Health Policy (CCHP) — federal and state-by-state telehealth policy
- National Association of Rural Health Clinics (NARHC) — RHC-specific telehealth guidance
- HHS telehealth.hhs.gov — federal policy and best-practice guides
EHR integration
MedConnect works alongside your EHR rather than replacing it. Integration options include a server-to-server REST and GraphQL API for patient and examination data, HL7 2.x and GDT for device data, and FHIR R4 exchange for vital signs data via AIView. ECG reports arrive as PDFs attached to the consultation automatically. The exact interface to your EHR is scoped during solution design with your IT lead.
Security and privacy
- HIPAA-ready: we sign a Business Associate Agreement (BAA).
- US hosting: US customer data is hosted on AWS in the United States (us-east-1).
- ISO 27001:2022 certified (British Assessment Bureau).
- Encrypted video: sessions run on the AWS Chime SDK with end-to-end encryption.
More detail on the telehealth compliance page.
Delivery, training and support
We ship the configured equipment directly to each site, train your team remotely and provide remote support. We do not have a US distributor or an on-site installation team, so the rollout plan names a local contact at each site to unpack, connect and run the first test session with us.
Funding
Many clinics finance telehealth equipment through grants, including state subgrants under the Rural Health Transformation Program and federal programs from HRSA, USDA and the FCC. Eligibility is decided by each program and state, not by MedConnect. Our Rural Health Transformation Program telehealth guide summarizes what the program funds and how equipment money reaches clinics.
Procurement checklist for RHCs and FQHCs
- Which visit types will you run remotely, and which need a live physician vs store-and-forward review?
- How many sites, exam rooms and outreach teams—and which format fits each (station, cart, kit)?
- Which devices does each visit type require, and do you need FDA status and component documentation for your file?
- Who are your telepresenters, what are their credentials, and how will you document their training?
- Which EHR and billing system must the platform connect to, and through which interface?
- Has your compliance team reviewed the BAA, US hosting and access controls?
- Has someone validated current originating/distant-site and payer rules with CCHP, NARHC or HHS?
- Who receives the shipment at each site and leads the remote onboarding?
Related solutions
Solution design
Request a configured quote
Pricing is quote-based. It depends on the number of sites and formats, the device set per site, the number of physician and telepresenter users, the EHR interface and the training plan. Tell us about your sites and visit types and we will scope the configuration.
- ✓ Station, cart and kit mix per site
- ✓ FDA-cleared and FDA-registered device set
- ✓ EHR interface and BAA review
- ✓ Remote telepresenter training and support
Frequently asked questions
What is the best telehealth setup for a rural health clinic where a nurse presents the patient to a remote physician?
A nurse-presented (telepresenter) setup: secure video software that carries two streams—the patient’s face and the live device feed—plus connected exam devices the nurse uses at the physician’s direction: a vital signs monitor, an electronic stethoscope, a 12-lead ECG and an otoscope or exam camera. MedConnect packages these as a fixed station, a telehealth cart or a portable kit, with live and store-and-forward consultations.
Which connected diagnostic devices does the US basic kit include, and are they FDA-cleared?
The US basic kit combines FDA-cleared and FDA-registered devices: the Edan iM3s vital signs monitor (510(k) K202892 / K233038), the Edan SE-1515 12-lead PC ECG (510(k) K152427), the Riester ri-sonic USB electronic stethoscope (510(k) K132560), and Firefly digital otoscope and exam cameras, which are Class I, 510(k)-exempt and FDA-registered. Component documentation is available on request.
Does MedConnect handle telehealth billing for RHCs or FQHCs?
No. MedConnect does not do billing or claims and makes no reimbursement claims. Your clinic keeps its own EHR and billing system, and MedConnect connects to it. Originating-site and distant-site rules for RHCs and FQHCs vary by payer and state and change over time, so your organization should validate them with sources such as CCHP, NARHC and HHS.
Can one physician or specialist cover several clinic sites?
Yes, that is a common hub-and-spoke pattern. Each spoke site has a station, cart or kit and a trained telepresenter; the clinicians your organization already works with join from the hub. The platform’s virtual waiting room, multi-practitioner scheduling and multi-site administration let one provider see queued patients from several locations.
Does MedConnect integrate with our EHR?
MedConnect exposes a server-to-server REST and GraphQL API for EHR integration, supports HL7 2.x and GDT for device data, and FHIR R4 exchange for vital signs data via AIView. The ECG PDF is attached automatically to the consultation record. The exact interface with your EHR is scoped during solution design.
Is MedConnect HIPAA-ready, and where is US data hosted?
MedConnect is HIPAA-ready and we sign a Business Associate Agreement (BAA). US customer data is hosted on AWS in the United States (us-east-1). Promotal is ISO 27001:2022 certified, and video sessions run on the AWS Chime SDK with end-to-end encryption.
How is the equipment delivered, set up and supported in the US?
We ship the configured equipment directly to your clinic, train your team remotely and provide remote support. There is no US distributor or on-site installation team, so the rollout plan accounts for who unpacks, connects and tests each station locally.