Programming Fundamentals (Python / JS / C)
MedTech leans on Python (data/AI), JS/TypeScript (Web/App), and C/C++ (device firmware).
A skill map for non-clinical career changers entering MedTech / Digital Health in Taiwan (2024-2026)
29 result(s)
MedTech leans on Python (data/AI), JS/TypeScript (Web/App), and C/C++ (device firmware).
Front/back-end for hospital information systems (HIS), patient apps, telemedicine platforms, and health-management UIs.
Deploying healthcare apps on AWS/GCP/Azure, with compliant storage and access control for medical data.
SQL/NoSQL plus healthcare-specific structures such as EHR, lab results, and imaging metadata.
Version control, automated testing, and CI/CD, which in device software must map to IEC 62304's traceable processes.
MCU firmware, I2C/SPI comms, and biosignal sensor integration, the low level of wearables and bedside instruments.
NumPy/Pandas/Matplotlib plus scikit-learn, the lingua franca of medical data analysis.
Supervised/unsupervised learning, evaluation, and overfitting control, with healthcare emphasizing interpretability and calibration.
CNN/Transformer with TensorFlow/PyTorch, the workhorse for medical imaging and signal analysis.
Reading/writing the DICOM format, PACS concepts, and preprocessing for imaging AI.
NLP and information extraction over clinical notes, lab reports, and nursing records.
Building pipelines to extract, clean, and integrate data from HIS, sensors, and wearables.
Hypothesis testing, regression, survival analysis, and statistical literacy for clinical study design.
A functional grasp of body systems, enough to understand what a product measures or assists.
Reading the abbreviations and word-roots on records and lab orders, the minimum for cross-domain communication.
The real flow from registration to consult, orders, labs, treatment, and discharge, and clinicians' time pressure.
How hospital systems (HIS/EMR/PACS/LIS) interconnect, plus procurement and deployment realities.
Do-no-harm principles, error taxonomies, alert fatigue, and human factors, the core value system of medical software.
Deciding whether your software is a medical device and which risk class, which sets the entire regulatory path.
The QMS baseline for device companies, covering design/development, document control, and post-market surveillance.
The development-process standard for device software, with three safety classes (A/B/C).
The risk-management framework for devices, tightly coupled with 13485 design and 62304 software processes.
Taiwan TFDA device registration, AI/ML device guidance, and Predetermined Change Control Plans (PCCP).
Personal Data Protection Act, de-identification of medical data, access control, and security governance.
The modern standard for health-data exchange (FHIR), letting different systems talk.
The transmission/storage standard for medical imaging, the basis of imaging-system interoperability.
Collaborating with clinicians, regulators, and hospital IT, the scarcest soft skill and the one that most decides success.
Designing safe, usable interfaces for high-stress, fatigue-prone clinical settings, where usability is patient safety.
Driving products under regulatory and quality constraints, coordinating engineering, clinical, regulatory, and market.