Engineering a pharmacy-based telemedicine platform for remote clinical examination, live consultation, records, prescriptions and fulfilment in France
Anonymized NDA engagement — production platform in France
Keywords: Telemedicine; connected medical devices; community pharmacy; EMR; PHR; Sampark; remote consultation; HDS; GDPR; digital prescription; healthcare platform engineering.
This article is based on anonymized internal case-study material. The client operates under a non-disclosure agreement; therefore no client name, logo, website or identifying detail is included.
Abstract
This case study examines the design and delivery of a production-grade telemedicine platform for a France-based digital-health company. The solution connects community pharmacies, a connected medical examination device and a dedicated physician network through one secure software platform. It enables patients to walk into a pharmacy, complete guided intake, consult a remote physician through live video, share diagnostic readings in real time, receive a clinical report and obtain a digital prescription through pharmacy or logistics fulfilment.
NoteG Technologies acted as the end-to-end engineering partner for the platform. The engagement covered patient, doctor and pharmacy experiences; appointment booking; speciality-based doctor discovery; connected-device integration; EMR and PHR systems; clinical reports; digital prescriptions; pharmacy dispensing and logistics; reporting and analytics; and Sampark as the real-time video consultation layer.
Headline finding: the platform is not a pilot. It has supported more than two million teleconsultations in a compliant production environment, demonstrating that pharmacy-based telemedicine can scale when clinical workflows, connected devices, records, prescriptions, fulfilment and real-time communication are engineered as one integrated system.
1. Introduction
Primary care access is increasingly constrained by long appointment lead times, overloaded clinics and regional gaps in physician availability. The client's model addresses this problem by moving the first point of access into community pharmacies, where patients already have a local, trusted and walk-in healthcare touchpoint.
The central concept is simple: a patient visits a participating pharmacy, is assisted by pharmacy staff, uses a touchscreen tablet and connected diagnostic device, and consults a physician remotely within minutes. The physician receives live video, patient intake information and examination readings during the same encounter, then completes documentation and prescription generation inside the platform.
From an engineering perspective, this is not a conventional video-consultation product. It requires reliable real-time communication, device integration, clinical record management, secure prescription workflows, pharmacy fulfilment and strict health-data compliance. Each part must work with the others without interrupting the clinical journey.
2. Client context and operating model
The client is an anonymized French digital-health company. Its operating model places teleconsultation inside a nationwide network of community pharmacies rather than positioning patients as isolated online users. Pharmacies become assisted points of care, enabling patients to complete a physical examination with remote physician oversight.
| Operating element | Role in the care model |
|---|---|
| Community pharmacy | Local walk-in point of care where staff assist the patient and initiate the consultation. |
| Touchscreen tablet | In-pharmacy interface for identity, intake, consultation launch and guided patient flow. |
| Connected medical device | Diagnostic device bundling instruments such as stethoscope, thermometer, otoscope, dermatoscope and pulse oximeter. |
| Physician network | Dedicated panel of 200+ physicians available for speciality-based teleconsultation. |
| Secure software platform | The application, data and communication layer built by NoteG Technologies to orchestrate the full journey. |
Because sensitive medical information is stored and processed in France, the platform was designed for HDS health-data hosting and GDPR/RGPD compliance from the beginning.
3. Problem statement
The engagement required more than feature delivery. It required a complete clinical platform that could support real consultations at national scale, in pharmacies with variable connectivity, while maintaining continuity of care and regulatory-grade data protection.
| Challenge area | Engineering requirement |
|---|---|
| Complete clinical platform | Build patient, doctor and pharmacy workflows, booking, consultations, reports, prescriptions, fulfilment and analytics as one coherent system. |
| Secure clinical data backbone | Design EMR and PHR systems with protected health information controls, structured records and reliable data integrity. |
| Medical-grade live video | Support low-bandwidth pharmacy environments without turning the consultation into a fragile video call. |
| Connected-device integration | Capture readings from multiple instruments during the live session and preserve them in the clinical record. |
| Compliance by design | Build consent, privacy, access control and health-data hosting requirements into architecture rather than adding them later. |
| Scale and concurrency | Sustain simultaneous consultations across pharmacies and physicians as usage grows into millions of sessions. |
| Speed to market | Allow the client to focus on clinical operations, pharmacy partnerships and hardware while NoteG owned the software and real-time engineering. |
Design implication: the platform had to behave like a clinical operating system for pharmacy teleconsultation, not like a collection of separate applications connected after the fact.
4. Engagement scope
NoteG Technologies served as the client's end-to-end product engineering partner. The engagement covered the complete platform from experience design and workflow logic to clinical data handling, connected-device integration, real-time video, analytics and compliance implementation.
| Scope area | Delivered capability |
|---|---|
| Patient, doctor and pharmacy experiences | Role-specific interfaces supporting intake, consultation, clinical action, pharmacy launch and dispensing. |
| Appointment booking and doctor discovery | On-demand and scheduled appointments routed by speciality and real-time availability. |
| Connected medical-device integration | Live instrument readings streamed to the physician and attached to the clinical record. |
| EMR and PHR systems | Structured patient histories, consultation records, reports, device readings and prescriptions. |
| Clinical reporting and prescription generation | Structured documentation and digital prescriptions generated within the consultation flow. |
| Pharmacy dispensing and logistics | Prescription fulfilment linked to pharmacy operations or onward logistics. |
| Reporting and analytics | Operational visibility across consultation volumes, network performance and platform activity. |
| Sampark real-time layer | Live video-consultation capability engineered for low bandwidth, multilingual use and high concurrency. |
| Compliance architecture | HDS- and GDPR-aligned design covering privacy, access control, consent and secure data handling. |
5. Platform design and implementation
The platform was designed around the end-to-end care journey. Each module serves a clinical or operational function, but the value comes from the way the modules are connected: intake becomes doctor context, device readings become clinical evidence, prescriptions become fulfilment instructions, and all outcomes return to the patient record.
| Platform layer | Primary function | Implementation result |
|---|---|---|
| Patient experience | Identity, intake, guided consultation and post-consultation hand-off. | Built as an assisted in-pharmacy tablet flow. |
| Doctor experience | Patient history, live device readings, video, documentation and prescription tools. | Built as a unified physician workstation. |
| Pharmacy interface | Launch consultations, support patients, track activity and manage dispensing. | Built as an operational pharmacy console. |
| Doctor discovery | Match patients to physicians by symptoms, speciality and availability. | Built for on-demand and scheduled access. |
| Consultation engine | Coordinate session state, participants, records, reports and prescriptions. | Built as the orchestration layer. |
| Clinical data systems | Store EMR, PHR, reports, prescriptions and device data securely. | Built with PHI-grade access and data integrity controls. |
| Analytics layer | Provide operational reporting and visibility across the network. | Built for monitoring, optimization and scale. |
Implementation principle: a consultation should feel simple to the patient, but every step behind that simplicity should be structured, auditable and clinically useful.
6. System architecture
The architecture was organized in layers to separate physical pharmacy operations, role-based interfaces, consultation orchestration, clinical data, real-time communication and compliance controls. This structure allowed the client to scale pharmacy deployments and physician participation without rebuilding the core platform.

| Layer | What it does | Delivery status |
|---|---|---|
| Connected medical device | Captures remote-exam readings from stethoscope, thermometer, otoscope, dermatoscope and oximeter. | Integrated |
| Patient / doctor / pharmacy interfaces | Provides the end-to-end consultation experience for all participants. | Built |
| Booking + doctor discovery | Matches patients to physicians by speciality, availability and appointment mode. | Built |
| Consultation engine | Orchestrates the live encounter, data capture, documentation and session completion. | Built |
| Real-time video — Sampark | Powers the live doctor-patient consultation with reliability and scale requirements. | Built + integrated |
| Clinical reports + prescriptions | Generates structured reports and digital prescriptions inside the clinical workflow. | Built |
| EMR + PHR | Maintains structured clinical records and patient-centric health information. | Built |
| PHI security + HDS/GDPR | Supports regulatory-grade privacy, protection and access control. | Designed in |
7. Sampark real-time consultation layer
Every live doctor-patient consultation runs on Sampark, NoteG Technologies' real-time communication platform. In this case, Sampark is a clinical reliability layer rather than a generic video plug-in. Its purpose is to keep consultations usable across the real-world network conditions of pharmacies while supporting simultaneous national-scale activity.
| Capability | Role in the telemedicine platform |
|---|---|
| Low-bandwidth handling | Maintains stable consultations on weak and variable pharmacy connections, degrading gracefully rather than dropping the session. |
| Multilingual support | Supports consultations across multiple languages and a diverse patient population. |
| High concurrency | Supports large volumes of simultaneous consultations across the pharmacy and physician network. |
| Interactive intelligence layer | Extends live video into an enriched consultation environment rather than a passive communication pipe. |
Clinical relevance: in telemedicine, video reliability is not only a user-experience concern. A frozen or failed session can interrupt examination, diagnosis, documentation and patient confidence.
8. Compliance and security approach
The platform handles sensitive medical data in France, so data protection and health-data hosting requirements were not treated as late-stage documentation. They were designed into the architecture, access model and clinical workflows from day one.
| Control area | Platform treatment |
|---|---|
| HDS health-data hosting | Data handling was built to operate within certified French health-data-hosting requirements. |
| GDPR / RGPD | Privacy, consent, confidentiality, access control and user rights were addressed within the EMR, PHR and consultation flows. |
| Role-based access control | Patient, physician, pharmacy and administrative roles are separated so users access only what they need. |
| Clinical data integrity | Consultation records, device readings, reports and prescriptions are preserved as structured clinical evidence. |
| PHI-grade protection | Protected health information is governed through appropriate access controls and safeguards throughout the system. |
9. Operational workflows
The platform converts a pharmacy visit into a structured teleconsultation pathway. The workflows below show how the patient journey, doctor routing, clinical documentation and fulfilment path are connected.


10. Documentation, prescription and fulfilment
Clinical closure was designed as part of the consultation, not as a separate administrative afterthought. The physician can complete documentation, generate the report, issue the prescription and trigger fulfilment through one connected process.

| Workflow output | Why it matters |
|---|---|
| Clinical report | Creates a structured, stored record of the consultation and physician assessment. |
| Device readings | Preserves remote examination evidence alongside the clinical encounter. |
| Digital prescription | Moves from physician order to fulfilment path without manual transcription. |
| Fulfilment status | Keeps pharmacy/logistics outcome connected to the patient record. |
| EMR/PHR sync | Supports future consultations with updated clinical history and continuity of care. |
11. Results and impact
The strongest outcome is sustained production usage. Since inception, the platform has powered more than 2,000,000 cumulative teleconsultations. This shows that the system reached a level of reliability, usability and operational fit beyond pilot validation.
| Impact area | Outcome |
|---|---|
| Teleconsultation volume | 2,000,000+ cumulative consultations delivered through the platform since inception. |
| Production completeness | End-to-end journey from booking to consultation, reporting, prescription and fulfilment. |
| Clinical communication reliability | Sampark provided the live consultation layer for low-bandwidth, multilingual and high-concurrency use. |
| Compliance foundation | HDS- and GDPR-compliant environment supported by EMR, PHR and PHI protection controls. |
| Client focus | The client could focus on clinical model, pharmacy network and connected device while NoteG owned software and real-time engineering. |
The project demonstrates NoteG Technologies' ability to deliver a regulated, high-scale healthcare platform where hardware, live video, clinical data, pharmacy workflow and analytics must operate as one system.
12. Discussion and conclusion
The case illustrates three important lessons for telemedicine platform delivery. First, access innovation depends on physical workflow design as much as software. Second, real-time communication is a clinical infrastructure component. Third, compliance must shape the system from day one.
| Lesson | Implication for future healthcare platforms |
|---|---|
| Design around the care setting | Digital products must fit the operational reality of pharmacies, physicians and assisted patients. |
| Treat real-time video as clinical infrastructure | Reliability, concurrency and network resilience directly affect quality of care. |
| Integrate records and devices early | Remote examination becomes clinically valuable only when readings are visible live and stored properly. |
| Build compliance into architecture | HDS/GDPR, access control and data protection are system-design requirements, not documentation tasks. |
| Engineer for scale before scale arrives | Millions of consultations require careful design of concurrency, data flows, analytics and operational support. |
NoteG Technologies delivered the software and real-time engineering foundation for a national-scale connected-device teleconsultation platform in France. The engagement covered the full clinical and operational journey: patient intake, doctor discovery, live video consultation through Sampark, device reading integration, EMR/PHR, reports, prescriptions, pharmacy/logistics fulfilment, analytics and compliance architecture.
The platform proves that pharmacy-based telemedicine can move beyond a lightweight video call into a complete assisted clinical pathway. Its impact is reflected in the volume and continuity of real usage: more than two million consultations delivered through the system since inception.
Closing note
The measure of this case is not a concept note or pilot slide. It is sustained clinical usage at scale, powered by an integrated platform built for real-world care delivery.