Master’s in Telemedicine, IoMT and Clinical Platforms Engineering
Online master's programme of 1,900 hours in telemedicine, IoMT and clinical platforms engineering. 12 modules covering remote care models, IoMT architecture, interoperability with IEEE 11073 and HL7 FHIR, telemonitoring, teleconsultation, cybersecurity, privacy, device and software regulation, remote data analytics and implementation, with an assigned technical tutor.
Take the controls.
Run a real engineering trade-off from this field. Move the sliders, watch the model react in real time and beat the challenge.
What you will be able to do
Design evidence-based telemedicine care models.
Build scalable and secure IoMT architectures.
Integrate devices using IEEE 11073 and HL7 FHIR.
Implement telemonitoring programmes with effective alerts.
Protect the cybersecurity and privacy of clinical platforms.
Apply medical device regulation to connected platforms.
Evaluate implementation with models such as MAST.
Who it's for
- Telemedicine platform engineers building remote care services.
- IoMT architects designing connected device ecosystems.
- Interoperability specialists working with IEEE 11073, FHIR and IHE profiles.
- Telemonitoring programme coordinators in hospitals and health services.
- Healthcare cybersecurity engineers.
- Connected health product managers.
- Engineering or science graduates seeking to enter health services.
What you'll work with
- Regulation (EU) 2017/745 (EU Medical Device Regulation, MDR)
- ISO/IEEE 11073 (personal health device communication)
- HL7 FHIR R4 (health data interoperability)
- IEC 80001-1 (IT networks incorporating medical devices)
- IEC 81001-5-1 (cybersecurity of health software)
- Regulation (EU) 2016/679 (GDPR, data protection)
- Law 41/2002 (Spanish law on patient autonomy and clinical records)
- Directive (EU) 2022/2555 (NIS2, network and information security)
- AWS IoT Core
- Azure Health Data Services
- HAPI FHIR
- Node-RED
- Grafana
12 modules · 1900 h
1.1Synchronous and asynchronous telemedicine modalities1.2Teleconsultation, telemonitoring and specialist teleconsultation1.3Clinical evidence for telemedicine1.4Hybrid care models1.5Telemedicine in chronic diseases1.6Rural telemedicine and access1.7Hospital at home1.8Patient experience in remote care1.9Cultural barriers and the digital divide1.10Case study: redesign of a heart failure clinic
2.1Device, gateway and cloud layers2.2Connected medical devices2.3Mobile gateways and home hubs2.4BLE, MQTT and CoAP protocols2.5Cloud IoT platforms2.6Scalability and high availability2.7Microservice architectures2.8Logistics and replacement of home devices2.9Platform monitoring2.10Laboratory: MQTT gateway for a blood pressure monitor
3.1IEEE 11073 device profiles3.2Continua and the Personal Connected Health Alliance3.3HL7 FHIR for observations3.4IHE PCD and POU profiles3.5Integration with the health record3.6LOINC and SNOMED CT terminologies3.7Patient and device identification3.8Interoperability testing3.9Open APIs and ecosystems3.10Practical: mapping glucose readings to FHIR Observation
4.1Chronic patient monitoring programmes4.2Clinical thresholds and alerts4.3Nurse triage of alerts4.4COPD and heart failure monitoring4.5Diabetes and continuous glucose monitoring4.6Post-operative monitoring after early discharge4.7High-risk pregnancy and paediatrics4.8Managing false positives4.9Clinical outcome indicators4.10Case study: alert protocol for COPD
5.1Video consultation platforms5.2Audio and video quality5.3Remote physical examination5.4Tele-examination devices5.5Teledermatology and teleophthalmology5.6Telepsychiatry and remote mental health5.7Documentation of the teleconsultation5.8Consent and communication5.9Good practice in digital etiquette5.10Practical: dermatology teleconsultation protocol
6.1Threats to connected devices6.2IEC 81001-5-1 and the secure life cycle6.3Cloud security and the Spanish National Security Framework (ENS)6.4Authentication and identity management6.5End-to-end encryption6.6IoMT penetration testing6.7The NIS2 Directive in the health sector6.8Incident response6.9Supply chain security6.10Workshop: threat analysis of an IoMT platform
7.1GDPR legal bases in telemedicine7.2Health records and information under Law 41/20027.3Professional liability in telemedicine7.4Remote prescribing7.5Cross-border telemedicine and Directive 2011/24/EU7.6Data processors and the cloud7.7Data protection impact assessment7.8Record retention7.9Medical code of ethics7.10Case study: data processing agreement
8.1Regulation (EU) 2017/745 applied to platforms8.2Rule 11 and monitoring software8.3Systems and procedure packs8.4IEC 62304 in platform software8.5IEC 60601-1-11 home healthcare devices8.6ISO 14971 in connected systems8.7IEC 80001-1 medical IT networks8.8Incident vigilance for connected platforms8.9FDA pathway for remote monitoring8.10Practical: classification of a telemonitoring platform
9.1Physiological time series9.2Detection of clinical deterioration9.3Predictive models of decompensation9.4Smart alerts and prioritisation9.5Dashboards for clinical teams9.6Patient data quality9.7Adherence to device use9.8Machine learning in IoMT9.9Evaluation of alert performance9.10Laboratory: decompensation alert model
10.1Designing apps for patients10.2Accessibility and digital literacy10.3Patient onboarding and training10.4Interfaces for professionals10.5Clinical team workload10.6Usability validation according to IEC 62366-110.7Patient involvement in design10.8Adherence and motivation techniques10.9Satisfaction assessment10.10Practical: usability test with older patients
11.1Organisational models for telemedicine11.2Telemonitoring control centres11.3Funding and reimbursement11.4Economic evaluation of telemonitoring11.5The MAST evaluation model11.6Change management11.7Training of professionals11.8Scaling and sustainability11.9Health outcome evaluation11.10Case study: MAST evaluation of a programme
12.1Care need and population12.2Proposed care model12.3Technical architecture of the platform12.4Integration and interoperability12.5Cybersecurity and privacy12.6Regulatory fit of the platform12.7Clinical and economic evaluation plan12.8Programme implementation plan12.9Master's Thesis report12.10Master's Thesis: defence before a panel
How you'll learn
100% online training on the SEIUM campus, with downloadable materials, recorded classes and an assigned technical tutor. There are no fixed timetables: you progress at your own pace within each intake, so the programme is compatible with work.
Each module combines theory, guided reading of the original standard and applied exercises. The working software is AWS IoT Core, Azure Health Data Services, HAPI FHIR, Node-RED and Grafana, in free, academic or evaluation versions. Practical work is based on real procedures: telemonitoring prototypes with real devices, integration of device data into FHIR and usability testing with patients. Assessment is continuous by module, plus the final Master's Thesis.
Standards covered: Regulation (EU) 2017/745 on medical devices, ISO/IEEE 11073, HL7 FHIR R4, IEC 80001-1, IEC 81001-5-1, Regulation (EU) 2016/679 (GDPR), Law 41/2002 on patient autonomy, Directive (EU) 2022/2555 (NIS2).
Build it end to end
Your final project follows the real engineering workflow, step by step, reviewed by your tutor.
Where this takes you
Requirements
- University degree in engineering, science or architecture, or equivalent demonstrable professional experience.
- Internet connection and a computer capable of running the programme software.
- English sufficient to read technical standards.
Ready to start?
Send your application today. Our admissions team replies within 72 hours with your study plan and funding options.
Frequently asked questions
The programme totals 1,900 hours over 12–14 months. You set your own pace within each intake, and your tutor helps you plan the workload around your job.
You work with AWS IoT Core, Azure Health Data Services, HAPI FHIR, Node-RED and Grafana, using free, academic or evaluation versions. Your tutor indicates the free alternative wherever one exists.
A SEIUM Institute diploma, awarded on passing the continuous assessment and the Master's Thesis. It is SEIUM's own qualification, not an official state degree; its recognition depends on the programme completed and the regulations of each country.
Yes. Modules passed in a course or postgraduate diploma in the same area are recognised in the higher programme. Ask about the recognition policy when you enrol.
A university degree in engineering, science or architecture (or equivalent professional experience), a computer able to run the software, and English sufficient to read technical standards.
Start dates are set by SEIUM's faculty for each intake. Our admissions team will confirm the next available date when you apply.
Related programmes
Master’s in Movement Neuromechanics and Musculoskeletal Modelling Engineering
Online master's programme of 1,900 hours in movement neuromechanics and musculoskeletal modelling engineering: 12 modules covering motor control neurophysiology, musculotendon mechanics, joint kinematics, neuromechanical data acquisition,…
Master’s in Usability and Human Factors Engineering for Devices
Online master's programme of 1,900 hours in usability and human factors engineering for medical devices. 12 modules covering human error, the IEC 62366-1 framework, user research,…
Master’s in HSE Management Engineering in Industry and Energy
Online master's programme of 1,900 hours in HSE Management Engineering in Industry and Energy, with 12 modules covering HSE in the industrial and energy sector, leadership…
More in Health, Biomechanics, Wearables & Operational Safety
All Health, Biomechanics, Wearables & Operational Safety programmes → · How to apply · Fees & financing · Scholarships