<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Software Quality and Compliance in Intelligent Health Monitoring Systems: A Case Study of Baby FM</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Bojan Gutić</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tamara Papić</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Pavle Dakić</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Informatics and Computing, Singidunum University</institution>
          ,
          <addr-line>Danijelova 32, 11000 Belgrade</addr-line>
          ,
          <country country="RS">Serbia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Faculty of Technical Sciences, Singidunum University</institution>
          ,
          <addr-line>Danijelova 32, 11000 Belgrade</addr-line>
          ,
          <country country="RS">Serbia</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Institute of Informatics, Information Systems and Software Engineering, Faculty of Informatics and Information Technologies, Slovak University of Technology in Bratislava</institution>
          ,
          <addr-line>Ilkovičova 2, 842 16 Bratislava</addr-line>
          ,
          <country country="SK">Slovakia</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>SQAMIA 2025: Workshop on Software Quality</institution>
          ,
          <addr-line>Analysis, Monitoring, Improvement, and Applications</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>Integrating artificial intelligence (AI) into wearable health monitoring systems introduces both innovation and regulatory complexity, requiring a standardized approach to ensure patient safety, software robustness, and compliance with international medical device regulations. This paper presents a comprehensive case study of Baby FM, an AI-powered wearable medical device developed for continuous temperature monitoring in pediatric and veterinary care. The system combines real-time sensing, secure cloud connectivity, and anomaly detection through interpretable AI models. We detail a structured approach to achieving high software quality through the implementation of a customized Quality Management System (QMS), in compliance with ISO 13485, ISO 14971, and IEC 62304. The QMS supported modular documentation, traceability, risk control, and test automation throughout the product life cycle. In addition, the study outlines the preparation of technical documentation for CE and ALIMS certification, including verification and validation evidence, clinical benefit justification, and post-market surveillance planning. Beyond the internal development and compliance strategy, this paper provides a comparative overview of standard adoption in multiple industries, including the med-tech, pharmaceutical, and industrial IoT sectors. This case study presents several key findings: Modular QMS implementation enabled incremental regulatory compliance without stalling agile software development, Early adoption of ISO 13485, ISO 14971, IEC 62304, and MDR 2017/745 reduced regulatory friction and aligned documentation with development milestones, Embedding explainable AI techniques (SHAP visualization and audit trails) improved transparency, clinician trust, and regulator acceptance. Comparative analysis confirms that medtech devices require more stringent certification than pharma and health IT but deliver stronger post-market accountability. The scalable architecture supports future extensions in oncology, fertility, and livestock monitoring. The findings illustrate how practices from these sectors can inform the development of intelligent health systems and guide strategic decisions for startups seeking certification. Insights from real-world clinical trials, regulatory interactions, and AI transparency strategies ofer a replicable methodology for innovators looking to balance agility and compliance in the development of AI-driven medical products.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Artificial Intelligence</kwd>
        <kwd>Software Quality</kwd>
        <kwd>AI in Healthcare</kwd>
        <kwd>Wearable Health Monitoring</kwd>
        <kwd>Risk Management</kwd>
        <kwd>CE Certification</kwd>
        <kwd>Baby FM</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        In the last decade, advances in wearable technologies have fundamentally reshaped the way health data
is collected and analyzed [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The convergence of miniaturized medical sensors, mobile applications,
and cloud-based platforms has enabled the development of patient monitoring systems that go far
beyond isolated measurements. Today’s intelligent devices deliver real-time insights, dynamic feedback
loops, and adaptive support for clinical decisions. This shift has been especially impactful in areas such
as neonatal [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and veterinary medicine, where even minor fluctuations in physiological signals can
precede visible symptoms and require timely intervention.
      </p>
      <p>
        The momentum behind wearable medical devices is driven by a combination of technical innovation
and systemic transformation in healthcare. Enhanced sensor accuracy, lower power consumption, and
user comfort have made continuous measurement feasible outside traditional clinical settings. At the
same time, advances in wireless protocols—such as Bluetooth Low Energy (BLE) and Narrowband
IoT (NB-IoT)—have made it possible to securely transmit patient data with minimal latency. These
capabilities are increasingly aligned with preventive, personalized medicine models, which rely on
ongoing monitoring rather than episodic clinical visits [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ]. However, as the capabilities of these
devices grow, so do the responsibilities of their developers. Manufacturers must ensure not only robust
performance, but also security, safety, and conformity with highly regulated development standards.
      </p>
      <p>The Baby FM system was created in response to a distinct clinical need: continuous, non-invasive
temperature tracking in infants and small animals, particularly in environments where access to care
is limited or periodic checks are insuficient. Baby FM comprises a CE-compliant wearable sensor, a
mobile application, and a cloud back-end that enables longitudinal monitoring, predictive alerts, and
integration with electronic health records. Unlike traditional thermometers or infrared devices, the
system allows for round-the-clock data collection, supports pattern recognition, and ofers clinicians
traceable, explainable outputs for decision-making.</p>
      <p>
        To navigate the regulatory landscape, the Baby FM team aligned its development approach with the
European Medical Device Regulation (EU MDR), under which the device qualifies as a Class IIa product.
This classification demands strict technical documentation, software validation, and implementation
of a formal Quality Management System (QMS). The process involved compliance with the following
standards:
• ISO 13485, which sets out the requirements for QMS specific to medical device manufacturers
and emphasizes documentation, traceability, and continuous improvement [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ].
• ISO 14971, which defines a structured framework for identifying and mitigating risk throughout
the product life cycle [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
• IEC 62304, which governs the entire life cycle of medical software, from requirements analysis to
testing, maintenance, and post-market support [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>To ofer a clearer understanding of how quality and safety standards are applied across diferent
industries, we included a comparative table based on sector-specific usage that can be found in Table 1
in Section 3.</p>
      <p>The focus is on standards like ISO 13485, ISO 14971, and IEC 62304, which are foundational in the
medical device field. Their implementation is also examined in related sectors such as pharmaceuticals,
digital health platforms, and industrial IoT. This comparison sheds light on how regulatory priorities
and technical expectations vary across domains, despite sharing similar goals related to reliability, risk
mitigation, and system integrity.</p>
      <p>
        Startups like Baby FM often face additional complexity due to limited resources and short development
cycles. Yet research has shown that a phased and modular approach to ISO 13485 implementation can
be both feasible and efective in early-stage environments [
        <xref ref-type="bibr" rid="ref5 ref9">5, 9</xref>
        ].
      </p>
      <p>This paper presents a structured case study of how Baby FM was designed, validated, and prepared
for certification. We explore the intersection of software quality, risk management, and cross-sectoral
standardization. Through this example, we aim to contribute actionable insights for technology
developers and medical innovators seeking to navigate the evolving field of intelligent health systems while
remaining compliant with national and international regulations.</p>
      <p>This paper is structured to lead the audience by way of a logical arrangement of thoughts and findings
that are as follows: Section 1 Introduction introduces the integration of AI in wearable medical devices
and outlines the objectives and scope of the Baby FM case study. Section 2 Materials and Methods
describes the system architecture, development tools, standards applied, and methodological framework
used throughout the study. Section 3 Literature Review This section reviews existing work on AI-driven
health monitoring, regulatory compliance, and quality management in medtech and related sectors.
Section 4 Certification Pathway and Technical File Preparation this section outlines the structured
process of preparing technical documentation for CE and ALIMS certification, including risk analysis
and verification evidence and details the design and deployment of a modular QMS aligned with ISO
13485, ISO 14971, and IEC 62304 to support development and compliance. Section 5 Results this section
presents the outcomes of QMS implementation, certification milestones, and the impact of explainable
AI on transparency and acceptance and evaluates the device’s clinical accuracy, market comparison, and
internal quality metrics. Section 6 Discussion: Lessons Learned and Strategic Trade-ofs reflects on the
practical challenges, key insights, and strategic decisions involved in balancing agile development with
regulatory demands. Section 7 Conclusion this section summarizes the case study’s key contributions
and ofers guidance for startups pursuing certification of AI-powered medical technologies.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Materials and Methods</title>
      <p>To acquire a thorough knowledge and methodology for the system architecture presented in this
document, a structured approach was used to infer links between components based on typical data
lfow patterns in IoT and healthcare systems.</p>
      <p>
        While clinical evaluation were carried out in partnership with two university-afiliated hospitals in
Belgrade: The Pulmonology Clinic and the Institute for Infectious and Tropical Diseases. These studies
validated system performance in clinical environments, focusing on accuracy, user comfort, and alert
responsiveness. The findings were compiled into a Clinical Evaluation Report (CER), meeting MDR
Annex XIV requirements [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>
        In our clinical trial, standard hospital gallium thermometer will be used along with our device by
applying comparative analysis. Clinical trial methodology was followed by ISO 14155 for planning and
execution, while all risk analyses were grounded in ISO 14971. Usability evaluations adhered to IEC
62366-1 [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], addressing interface design, alarm clarity, and minimizing user error. A Summary of Safety
and Clinical Performance (SSCP) was also prepared, supporting public transparency for CE-certified
devices [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>
        As Baby FM incorporates AI features, additional focus was given to documentation of model
transparency and traceability of used methodology. Collaboration with an experienced Notified Body led to
improvements in explainability of AI logic, training validation, and output interpretation. This was key
for meeting MDR Article 61 and Recital 48, which stressed the importance of justifiable and interpretable
software behavior [
        <xref ref-type="bibr" rid="ref13 ref14">13, 14</xref>
        ]. Parts related to the data aspect are further explained in Data Availability
Section 7.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Literature Review</title>
      <p>The past decade has seen a swift advancement in the incorporation of intelligent technologies within
healthcare systems, particularly with the increasing presence of AI-powered wearable and implantable
medical devices.</p>
      <p>These technologies now facilitate various clinical functions, including early detection of diseases
and ongoing patient monitoring, particularly in fields such as cardiology, oncology, pediatrics, and
post-operative care. Although the potential benefits are widely recognized, these innovations also raise
current issues regarding transparency, regulatory control, and integration into clinical practices.</p>
      <sec id="sec-3-1">
        <title>3.1. International standards as basis for the design, validation, and monitoring</title>
        <p>
          To tackle these issues, international standards ofer a systematic basis for the design, validation, and
monitoring of products after they enter the market. ISO 13485 [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] provides a framework for creating
and sustaining a Quality Management System (QMS) tailored to medical devices, emphasizing
decisionmaking based on risk and comprehensive documentation throughout the lifecycle. ISO 14971 [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]
enhances this by outlining approaches for recognizing, assessing, and managing risks at every phase of
a product’s existence. In the realm of software, IEC 62304 [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] outlines the requirements for development,
verification, and ongoing maintenance in applications where safety is critical, necessitating organized
software classification and traceability matrices.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Software Engineering Considerations for AI-Powered Wearables</title>
        <p>
          Wilmink et al. [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] demonstrated that the combination of wearable devices and AI-driven digital health
platforms can lead to better health management in assisted living communities, emphasizing the
potential for these technologies to support aging populations.
        </p>
        <p>
          Similarly, Porbundarwala et al. [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] reported positive health outcomes and increased user trust in
AI-driven health monitoring, underscoring the transformative impact of personalized health insights
provided by such devices. Furthermore, Alzghaibi [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] identified key factors influencing adoption,
including user education and trust, which are critical for integrating AI wearables into chronic disease
management.
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Quality and safety standards</title>
        <p>To provide a better understanding of how quality and safety standards are implemented across various
industries, a comparative analysis has been incorporated on the following Table 1.</p>
        <p>It illustrates that, although ISO 13485, ISO 14971, and IEC 62304 are well-established in the medical
device industry, other sectors such as pharmaceuticals, health IT, and industrial IoT focus on diferent
elements like cybersecurity (ISO/IEC 27001) or data integrity. This diversity highlights the distinctive
regulatory objectives and risk profiles of each sector.</p>
        <p>
          The growing interconnection of AI technologies across various sectors has led both regulators and
researchers to reevaluate how healthcare software is classified. A significant development in this area is
the European Union’s Artificial Intelligence Act, which sets forth new requirements for AI systems based
on their purpose and associated risk levels. In the realm of healthcare, in regard to European Union
Artificial Intelligence Act for Healthcare [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ] software is now divided into three primary categories:
        </p>
        <sec id="sec-3-3-1">
          <title>1. AI systems that are integrated into a certified medical device</title>
          <p>2. Supplementary or companion software that aids a medical device without being essential to its
operation
3. Independent software that executes a medical function on its own, identified as Software as a</p>
          <p>Medical Device (SaMD)</p>
          <p>Each of these categories necessitates a specific approach to compliance. Embedded systems need to
comply with both the Medical Device Regulation (MDR) and IEC 62304, ensuring traceability throughout
their lifecycle and adherence to device-level safety measures. Support software is often required to
meet GDPR and ISO/IEC 27001 standards, particularly when it deals with sensitive health information,
and must demonstrate usability and risk management through ISO/IEC 62366 and ISO/IEC 25010.</p>
          <p>Software as a Medical Device (SaMD) faces the most rigorous regulatory oversight under the AI
Act because of its ability to make autonomous decisions. It must be clearly transparent, auditable,
explainable, and clinically validated prior to its implementation.</p>
          <p>
            The policy report by AIHTA [
            <xref ref-type="bibr" rid="ref19">19</xref>
            ] highlights the necessity for harmonization of standards, particularly
in relation to post-market monitoring of adaptive AI systems. Additionally, emerging frameworks
increasingly promote continuous oversight, version management, and impact evaluation for any AI
model linked to or integrated with a regulated medical function.
          </p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Certification Pathway and Technical File Preparation</title>
      <p>
        The classification of Baby FM under the European Union Medical Device Regulation (EU MDR) 2017/745
was based on the device’s intended use for continuous temperature monitoring and its potential
diagnostic impact. As outlined in Rule 10 of Annex VIII [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ], Baby FM falls under Class IIa, since it monitors
physiological parameters that may influence clinical decisions. This categorization requires
comprehensive regulatory engagement, including conformity assessment by a Notified Body, documented clinical
evaluation, and a structured post-market surveillance framework.
      </p>
      <p>During the early stages of development, the Baby FM team mapped out its regulatory strategy to
ensure full alignment with the General Safety and Performance Requirements (GSPRs) defined in Annex
I of the MDR. A detailed checklist was developed to collect and track all compliance-related evidence,
laying the groundwork for the Technical Documentation needed for CE marking and domestic market
authorization via Serbia’s national regulatory body, ALIMS.</p>
      <p>
        The technical documentation was compiled by MDR Annexes II [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] and III [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ], and it included:
• Formal description of the intended use, patient group, and clinical value
• Risk documentation consistent with ISO 14971, covering usability and risk mitigation
• Comprehensive software design overview, supported by cybersecurity threat modeling
• Verification and validation records linked to specific system requirements
• Full labeling, packaging, and Instructions for Use (IFU) tailored to clinical and home users
All documentation was structured using the IMDRF Table of Contents (ToC) model to support
international regulatory compatibility. The Device Master Record (DMR) included the Bill of Materials
(BoM), design schematics, source code summaries, and a documented update history. Cybersecurity
was treated as a key area, incorporating encryption protocols, firmware protection mechanisms, and
access control strategies in line with MDCG 2019-16 recommendations [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ].
      </p>
      <p>
        Supplementary documentation included:
• A Software Bill of Materials (SBOM) covering all third-party and open-source components
according to NTIA [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]
• A Data Protection Impact Assessment (DPIA) aligned with GDPR Article 35 [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ]
• Clinical testing results and caregiver interaction mapping in regard to FDA [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ]
• Supplier audits and visual documentation of the manufacturing process according to ISO 13485 [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
Baby FM’s software outputs were supported by clinician-facing dashboards displaying decision
pathways, confidence scoring, and input-output relationships. Training routines were maintained
with reproducibility audits and version tracking. Software updates followed a defined validation and
deployment protocol consistent with IEC 82304-1 standards [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ] for medical-grade software life cycle
management.
      </p>
      <p>This rigorous documentation efort resulted in a fully compliant technical file, enabling Baby FM
to achieve both CE certification and national approval in Serbia. The approach demonstrates how
structured regulatory planning, proactive documentation, and multidisciplinary collaboration can help
startups achieve compliance in complex health technology markets.</p>
      <sec id="sec-4-1">
        <title>4.1. Quality Management System</title>
        <p>
          Implementing a Quality Management System (QMS) was an essential measure for aligning Baby FM
with medical device regulations and ensuring traceability throughout the development process. From
the beginning, the team chose ISO 13485:2016 [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] as the primary framework to support their compliance
initiatives.
        </p>
        <p>Recognizing the distinct challenges that early-stage startups encounter, the QMS was crafted to be
both flexible and modular. This strategy enabled the team to progressively fulfill necessary regulatory
milestones while still adhering to an agile, iterative development approach.</p>
        <p>Central to Baby FM QMS was a comprehensive set of documentation, including:
• Design and Development Plan (DDP)
• Software Requirements Specifications (SRS)
• Architecture and Modular Breakdown Document
• Verification and Validation Plan (VVP)
• Design History File (DHF)
• Device Master Record (DMR)
• Software Traceability Matrix and Risk Assessment Files</p>
        <p>Every one of these artifacts was designed with traceability and readiness for audits in mind. The
V-model was utilized to structure development stages, incorporating specific checkpoints that connect
design inputs with verification results.</p>
        <p>
          Baby FM closely followed the framework specified in IEC 62304 [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] for software validation, which
requires a software lifecycle process that includes planning, requirements analysis, architectural design,
implementation, testing, release, and maintenance.
        </p>
        <p>
          Risk analysis was performed in accordance with ISO 14971 [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ], identifying software-specific hazards
and mapping out control measures. A Risk Analysis Table (RAT), created and updated to meet ALIMS
and EU MDR standards, outlined mitigation strategies, potential risks, severity ratings, and thresholds
for risk acceptability. Examples of risks included the loss of data integrity from BLE disconnections,
incorrect temperature thresholds resulting in false negatives, or delays in clinical alerts due to cloud
service downtime. Each risk was thoroughly documented with a unique identifier, source traceability,
and connections to relevant mitigation procedures.
        </p>
        <p>
          Automated unit and integration testing were implemented to aid regression cycles, with coverage
metrics monitored via CI/CD pipelines [
          <xref ref-type="bibr" rid="ref28 ref29 ref30">28, 29, 30</xref>
          ]. End-to-end system testing encompassed realistic
usage scenarios that featured simulated fever conditions, hardware malfunctions, and user mistakes.
These tests were validated against expected system behavior and recorded in the Software Verification
Report (SVR). Test evidence was directly linked to requirement identifiers, ensuring traceability was
maintained.
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Results</title>
      <p>In the following sections, we give the findings from the analysis of the system architecture described in
the document. These findings demonstrate the structured interactions and data flows inside the B2C
and B2B frameworks, as well as the administrative monitoring capabilities.</p>
      <p>Model used in this case is gradient-boosted decision trees applied with XGBoost. Data is from the
deidentified 15 pulmonology patients from the pilot study. Model evaluation involves main performance
metrics on both training and validation datasets, including accuracy, precision, recall, F1 score, and
AUC.</p>
      <p>The UML class diagram eficiently depicts the relationships between essential components. This is
emphasizing their responsibilities and connectedness in producing a cohesive solution. This results
introduction prepares the groundwork for a thorough examination of the system’s functionality and
performance, providing insights into its operational eficiency and scalability.</p>
      <sec id="sec-5-1">
        <title>5.1. System Architecture and AI components for Baby FM</title>
        <p>The Baby FM platform is a comprehensive health monitoring system aimed at facilitating high-frequency,
non-invasive temperature monitoring for both pediatric and animal patients. Its design highlights the
integration of biomedical sensor technology, secure mobile communication, and cloud-based artificial
intelligence analytics.</p>
        <p>The system architecture is presented on the Figure 1 and comprises three interrelated components:
1. Compact wearable sensor
2. Mobile application serving as a gateway and user interface
3. Cloud-hosted AI engine along with a data repository</p>
        <p>Wearable Sensor
collectData()
sends data sends data</p>
        <p>sends data via BLE</p>
        <p>Mobile App
displayData()
sendDataToCloud()</p>
        <p>Parent Interface
viewChildData()</p>
        <p>Sensor Hub/BLE Module
transmitData()</p>
        <p>Admin Dashboard
viewAnalytics()
manageSystem()
uploads data retrieves data transmits data</p>
        <p>accesses data and analytics</p>
        <p>Cloud Backend
API
Database
storeData()
processRequests()
syncs data</p>
        <p>returns analytics sends data for analysis
EHR Integration
syncData()</p>
        <p>AI Module
Analytics Engine
analyzeData()
views analytics</p>
        <p>The sensor module features a high-accuracy temperature sensor that meets ISO 80601-2-56 standards
and is designed to measure core-equivalent skin temperature from one-second intervals with 0.1%
accuracy. It utilizes Bluetooth Low Energy (BLE) for wireless communication, ensuring low power
usage, which makes it ideal for overnight monitoring in both home and clinical settings. The casing of
the sensor is biocompatible and safe for skin contact, while the firmware is equipped with self-check
mechanisms and fallback error conditions in line with IEC 60601-1 electrical safety standards.</p>
        <p>
          The application is intended for both healthcare professionals and caregivers. It shows real-time
readings, trend charts, and alert notifications triggered by AI-detected anomalies. The application
utilizes on-device encryption with AES-128 before sending any data. Additionally, it incorporates
anonymization procedures and consent workflows that comply with GDPR standards. Clinical setups
facilitate the integration with Electronic Health Records (EHRs) via a secure RESTful API and modules
compatible with HL7 FHIR [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ].
        </p>
        <p>
          The AI component operating on the backend utilizes a cloud infrastructure to interpret temperature
patterns in real time. The system for detecting anomalies combines supervised learning, which
involves clinician-validated labels, with unsupervised clustering methods to diferentiate between normal
variations and significant medical deviations. A key aspect of this system is its interpretability layer,
which depicts the AI’s decision-making process through SHAP (SHapley Additive exPlanations) values
and audit logs. This not only enhances clinical confidence but also meets regulatory requirements for
transparency in AI systems, as specified in the EU AI Act [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ].
        </p>
      </sec>
      <sec id="sec-5-2">
        <title>5.2. Clinical Accuracy</title>
        <p>As illustrated in Figure 2, quantitative findings from a controlled clinical study conducted under ethical
approval comparing Baby FM with a gallium thermometer, Baby FM achieved ±0.1°C accuracy in 91.2%
of the cases.</p>
      </sec>
      <sec id="sec-5-3">
        <title>5.3. Market Comparison and limits of the study</title>
        <p>We have incorporated clinical carer feedback gathered during pilot trials in clinical settings at hospitals
afiliated with the University, even though formal veterinary usability studies are still in progress and
will be part of future work. The main concerns raised by the feedback were automated alert trust,
comfort during night time monitoring, and ease of use. Due to Baby FM’s continuous and non-invasive
measurement, more than 80% of participating carers preferred it over conventional oral or axillary
methods, according to the overwhelmingly positive informal feedback.</p>
        <p>In Table 2, we can see the comparison between Baby FM to industry-leading commercial temperature
monitoring systems like TempTraq®.</p>
      </sec>
      <sec id="sec-5-4">
        <title>5.4. Internal Quality Metrics</title>
        <p>• Unit test coverage: 94%
• Requirement-test traceability: 100%
• Avg. change request resolution: 2.5 days
• Monthly risk review updates since Q3 2024
These metrics help quantify our QMS eficiency and demonstrate adherence to continuous quality
monitoring protocols.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Discussion: Lessons Learned and Strategic Trade-ofs</title>
      <p>The development of Baby FM, an AI-powered medical device for continuous body temperature
monitoring, reveals a set of important insights for health technology innovators working in highly regulated
environments. This case exemplifies how early integration of regulatory principles, quality assurance
standards, and clinical usability requirements can serve not only as compliance measures but also as
drivers of product maturity and stakeholder trust. The Baby FM team faced a number of significant
obstacles throughout the development and certification process:
• To integrate DevOps pipelines with ISO 13485 requirements, formal branching, tagging, and audit
mechanisms must be established within CI/CD workflows.
• AI transparency: Designing visualisations (SHAP plots, confidence scores) to reveal model logic
was necessary to ensure clinical interpretability.
• Risk analysis: It was necessary to map cloud delays, BLE dropouts, and false temperature alerts
into risk tables that complied with ISO 14971.
• Documentation control: Git-based QMS tools and digital signatures were used to manage
document versioning and traceability because internal stafing was limited.</p>
      <sec id="sec-6-1">
        <title>6.1. Navigating AI Transparency and Clinical Interpretability</title>
        <p>
          Integrating artificial intelligence into a medical device adds a distinct layer of complexity. It is not
suficient for the algorithm to perform accurately—regulators and clinicians alike now expect
transparency, traceability, and explainability. In response to this, the Baby FM development included built-in
interpretability tools that translated model behavior into clear clinical signals. Visualization dashboards
were used to display input-output relationships, anomaly confidence scores, and historical signal context.
This approach addressed concerns outlined in the MDR [
          <xref ref-type="bibr" rid="ref14 ref21 ref22">21, 22, 14</xref>
          ] and anticipated future requirements
from the EU AI Act [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ], providing both auditors and users with meaningful insights into the algorithm’s
decision process.
        </p>
      </sec>
      <sec id="sec-6-2">
        <title>6.2. Regulatory Planning as an Ongoing Process</title>
        <p>Instead of viewing compliance as a final step, regulatory planning was integrated into every development
phase. The team utilized the General Safety and Performance Requirements (GSPRs) from the outset as a
guide for aligning design activities, verification tests, and risk evaluations. The technical documentation
was developed according to MDR Annexes II and III, while the use of the IMDRF Table of Contents
ensured compatibility with international submission formats. Clinical validation eforts were grounded
in ISO 14155 and ISO 14971, ensuring a continuous connection between pre-market data and post-market
expectations.</p>
      </sec>
      <sec id="sec-6-3">
        <title>6.3. Embedding Cybersecurity and Data Protection from the Start</title>
        <p>
          Given the nature of Baby FM as a connected device handling personal health data, cybersecurity and
privacy were not treated as add-ons but as design imperatives. The system architecture incorporated
AES-128 encryption, device-level authentication, and GDPR-compliant anonymization policies from
the prototyping stage. These elements aligned with ISO/IEC 27001 [
          <xref ref-type="bibr" rid="ref33">33</xref>
          ] and MDCG cybersecurity
recommendations and played a critical role in building user trust, especially in clinical settings dealing
with vulnerable pediatric populations.
        </p>
      </sec>
      <sec id="sec-6-4">
        <title>6.4. Sector Comparison and Regulatory Depth</title>
        <p>Compared to other segments of the health technology field, such as pharmaceutical software tools or
digital health services, the path to compliance for medical devices is significantly more demanding.
These devices are expected to meet strict, layered requirements that span from initial design to long-term
use in clinical environments. While some industries can apply quality and safety standards selectively,
medical device developers must demonstrate full regulatory alignment across engineering, software
safety, and patient risk management.</p>
        <p>As illustrated in Figure 3, medtech remains the most consistent adopter of standards like ISO 13485,
ISO 14971, and IEC 62304, reflecting a high level of traceability, system validation, and readiness for
global approval pathways.</p>
        <p>Medical Devices Health IT Pharma Industrial IoT
5</p>
        <p>3
2 1
ISO 14971
5</p>
      </sec>
      <sec id="sec-6-5">
        <title>6.5. Strategic Outcomes and Future Outlook</title>
        <p>The Baby FM experience confirms that small teams, even with limited resources, can navigate complex
certification pathways when compliance is built into the product strategy—not retrofitted. The decision
to invest early in quality systems, regulatory intelligence, and human-centered design significantly
reduced rework and accelerated engagement with clinical partners and regulatory reviewers. As
the company moves toward broader applications (e.g., oncology, fertility, veterinary use), the scalable
foundation established through these strategies will support both AI life cycle governance and regulatory
expansion.</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>7. Conclusion</title>
      <p>The development of Baby FM illustrates how startups in digital health can successfully navigate
regulatory and technical challenges by planning for compliance from the earliest stages.</p>
      <p>Instead of separating quality assurance from design, the team adopted a unified development model
that made safety, traceability, and documentation a natural part of the engineering workflow. In terms
of technical performance, Baby FM achieved a temperature measurement accuracy of ±0.1°C, with a
fever detection precision of 91.2% with the data extracted from the ongoing registered clinical study.</p>
      <p>Baby FM shows that responsible development - grounded in standards, focused on usability, and
aligned with regulatory logic - can help emerging health technologies succeed even in complex
environments.</p>
      <p>By relying on established international standards, the team was able to build a device that met both
clinical and regulatory expectations. This foundation made certification processes more eficient and
helped reduce delays during validation and review. Collaboration with medical professionals during
early testing also ensured that the system addressed real clinical needs.</p>
      <p>One of the system’s distinctive features is its use of interpretable artificial intelligence. Rather than
relying on opaque algorithms, Baby FM provides clear logic paths and visual tools that help users
understand how and why the device issues alerts. This transparency played an important role in the
building of trust between healthcare professionals and regulatory reviewers.</p>
      <p>Looking to the future, the core technology behind Baby FM is being extended to support new use
cases. These include temperature monitoring in oncology patients, integration with reproductive health
tools, and applications in animal care. Due to its modular structure, the system can be adapted to each
setting with minimal redesign, allowing faster rollout and easier validation.</p>
      <p>The company is also building a cloud-based service to connect its devices to hospital infrastructure.
Using established data exchange protocols, this platform will enable health institutions to incorporate
Baby FM into existing workflows, expanding its value as both a device and a data tool.</p>
      <p>This case highlights the importance of integrating quality thinking into innovation, especially in
AI-driven medical systems. As regulation becomes more demanding, particularly in areas involving
machine learning, the ability to document and explain system behavior will be key to clinical acceptance
and international growth.</p>
      <p>In further projects, Baby FM will further integrate software engineering, cloud-based AI, secure
mobile infrastructure, and biological sensing. Quality management systems will be in line with these
procedures. The platform will then be layered with architecture that ensures clinical safety, durability,
and regulatory compliance—demonstrating how software innovation for medical devices can be both
agile and compliant.</p>
    </sec>
    <sec id="sec-8">
      <title>Data availability</title>
      <p>In compliance with GDPR Articles 5 and 35, all patient data utilized in the creation and assessment of
Baby FM was anonymized. Temperature information is encrypted and saved locally on the user’s mobile
device when used at home. In clinical settings, information is sent to a hospital-controlled server via
secure channels for a de-identified assessment of comfort, safety, and efectiveness. Ethical Committee
of the Republic of Serbia granted ethics approval, and all clinical trials collected informed consent. Due
to patient confidentiality and regulatory compliance, data are not made publicly available; however,
synthetic datasets for research purposes may be made available upon request.</p>
    </sec>
    <sec id="sec-9">
      <title>Acknowledgments</title>
      <p>We thank Idvorski Laboratory for supporting EMC testing under IEC 60601-1 and Axiom International
for providing preliminary precision reports showing 0.1°C accuracy. Clinical Trial data is being collected
under NCT06447337 (https://clinicaltrials.gov/study/NCT06447337)</p>
    </sec>
    <sec id="sec-10">
      <title>Declaration on Generative AI</title>
      <sec id="sec-10-1">
        <title>The author(s) have not employed any Generative AI tools.</title>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A.</given-names>
            <surname>Mitek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Jones</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Newell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Vitale</surname>
          </string-name>
          ,
          <article-title>Wearable devices in veterinary health care</article-title>
          ,
          <source>Veterinary Clinics of North America: Small Animal Practice</source>
          <volume>52</volume>
          (
          <year>2022</year>
          )
          <fpage>1087</fpage>
          -
          <lpage>1098</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.cvsm.
          <year>2022</year>
          .
          <volume>05</volume>
          .001.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>H.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Xue</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Mei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. Bambang</given-names>
            <surname>Oetomo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <article-title>A review of wearable sensor systems for monitoring body movements of neonates</article-title>
          ,
          <source>Sensors</source>
          <volume>16</volume>
          (
          <year>2016</year>
          )
          <article-title>2134</article-title>
          . doi:
          <volume>10</volume>
          .3390/s16122134.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Tanaka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. S.</given-names>
            <surname>Mandour</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Shimada</surname>
          </string-name>
          , L. Hamabe,
          <article-title>Remote vital sensing in clinical veterinary medicine: A comprehensive review of recent advances, accomplishments, challenges, and future perspectives</article-title>
          ,
          <source>Animals</source>
          <volume>15</volume>
          (
          <year>2025</year>
          )
          <article-title>1033</article-title>
          . doi:
          <volume>10</volume>
          .3390/ani15071033.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>L.</given-names>
            <surname>Lu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Xie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Gao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Ye</surname>
          </string-name>
          ,
          <article-title>Wearable health devices in health care: Narrative systematic review</article-title>
          ,
          <source>JMIR mHealth and uHealth 8</source>
          (
          <year>2020</year>
          )
          <article-title>e18907</article-title>
          . doi:
          <volume>10</volume>
          .2196/18907.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>N.</given-names>
            <surname>Gasche</surname>
          </string-name>
          ,
          <string-name>
            <surname>Mastering</surname>
            <given-names>ISO</given-names>
          </string-name>
          <article-title>13485 certification as an agile medical startup - medium</article-title>
          .com,
          <year>2021</year>
          . URL: https://medium.com/biome-diagnostics/ mastering-iso-13485
          <string-name>
            <surname>-</surname>
          </string-name>
          certification
          <article-title>-as-an-agile-medical-start-up-dbe6215253cf.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>ISO</surname>
          </string-name>
          , ISO
          <volume>13485</volume>
          :2016 -
          <fpage>iso</fpage>
          .org,
          <year>2016</year>
          . URL: https://www.iso.org/standard/59752.html.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>ISO</surname>
          </string-name>
          , ISO
          <volume>14971</volume>
          :2019 -
          <fpage>iso</fpage>
          .org,
          <year>2019</year>
          . URL: https://www.iso.org/standard/72704.html.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>ISO</surname>
          </string-name>
          , IEC
          <volume>62304</volume>
          :2006 -
          <fpage>iso</fpage>
          .org,
          <year>2006</year>
          . URL: https://www.iso.org/standard/38421.html.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>M. F.</given-names>
            <surname>Lie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Sánchez-Gordón</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Colomo-Palacios</surname>
          </string-name>
          ,
          <article-title>Devops in an iso 13485 regulated environment: A multivocal literature review</article-title>
          ,
          <source>in: Proceedings of the 14th ACM / IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)</source>
          ,
          <source>ESEM '20</source>
          ,
          <string-name>
            <surname>ACM</surname>
          </string-name>
          ,
          <year>2020</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>11</lpage>
          . doi:
          <volume>10</volume>
          .1145/3382494.3410679.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10] MassimoP,
          <string-name>
            <surname>ANNEX XIV - Medical Device</surname>
          </string-name>
          Regulation - medical
          <string-name>
            <surname>-</surname>
          </string-name>
          device-regulation.eu,
          <year>2019</year>
          . URL: https://www.medical
          <article-title>-device-regulation</article-title>
          .eu/
          <year>2019</year>
          /08/14/annex-xiv/.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <source>[11] ISO, IEC 62366-1</source>
          :
          <fpage>2015</fpage>
          -
          <lpage>iso</lpage>
          .org,
          <year>2015</year>
          . URL: https://www.iso.org/standard/63179.html.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>MDCG</surname>
          </string-name>
          ,
          <article-title>Summary of safety and clinical performance A guide for manufacturers and notified bodies</article-title>
          ,
          <year>2022</year>
          . URL: https://health.ec.europa.eu/document/download/ 5f082b2f-8d51
          <string-name>
            <surname>-</surname>
          </string-name>
          495c
          <string-name>
            <surname>-</surname>
          </string-name>
          9ab9-985a9f39ece4_
          <fpage>en</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>B.</given-names>
            <surname>Corcoran</surname>
          </string-name>
          ,
          <source>EU MDR Article 61 Clinical Evaluation - MED</source>
          Institute - medinstitute.com,
          <year>2024</year>
          . URL: https://medinstitute.com/blog/eu-mdr-article-61
          <string-name>
            <surname>-</surname>
          </string-name>
          clinical-evaluation/.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>MDR</surname>
          </string-name>
          ,
          <article-title>Recitals 41 - 50 of the EU Medical Devices Regulation (MDR) - de-mdr-ivdr.tuvsud</article-title>
          .com,
          <year>2021</year>
          . URL: https://de-mdr-ivdr.tuvsud.com/Recitals-41-50.html.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>G.</given-names>
            <surname>Wilmink</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Dupey</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Alkire</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Grote</surname>
          </string-name>
          , G. Zobel,
          <string-name>
            <given-names>H. M.</given-names>
            <surname>Fillit</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Movva</surname>
          </string-name>
          ,
          <article-title>Artificial intelligence-powered digital health platform and wearable devices improve outcomes for older adults in assisted living communities: Pilot intervention study</article-title>
          ,
          <source>JMIR Aging 3</source>
          (
          <year>2020</year>
          )
          <article-title>e19554</article-title>
          . doi:
          <volume>10</volume>
          .2196/19554.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>T.</given-names>
            <surname>Porbundarwala</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Lalji</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Patil</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Dongardive</surname>
          </string-name>
          ,
          <article-title>Impact of ai in personalised health monitoring using wearable devices</article-title>
          ,
          <source>International Journal For Multidisciplinary Research</source>
          <volume>5</volume>
          (
          <year>2023</year>
          ). doi:
          <volume>10</volume>
          . 36948/ijfmr.
          <year>2023</year>
          .
          <year>v05i05</year>
          .
          <fpage>7144</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>H.</given-names>
            <surname>Alzghaibi</surname>
          </string-name>
          ,
          <article-title>Adoption barriers and facilitators of wearable health devices with ai integration: a patient-centred perspective</article-title>
          ,
          <source>Frontiers in Medicine</source>
          <volume>12</volume>
          (
          <year>2025</year>
          ). doi:
          <volume>10</volume>
          .3389/fmed.
          <year>2025</year>
          .
          <volume>1557054</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>F.</given-names>
            <surname>Busch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. N.</given-names>
            <surname>Kather</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Johner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Moser</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Truhn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. C.</given-names>
            <surname>Adams</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. K.</given-names>
            <surname>Bressem</surname>
          </string-name>
          ,
          <article-title>Navigating the european union artificial intelligence act for healthcare</article-title>
          ,
          <source>npj Digital Medicine</source>
          <volume>7</volume>
          (
          <year>2024</year>
          ).
          <source>doi: 10. 1038/s41746-024-01213-6.</source>
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <surname>AIHTA</surname>
          </string-name>
          ,
          <article-title>Artificial Intelligence in Health Care with a Focus on Hospitals: Methodological Considerations for Health Technology Assessment</article-title>
          ,
          <year>2024</year>
          . URL: https://eprints.aihta.at/1546/1/ HTA-Projektbericht_Nr.164.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20] MassimoP,
          <string-name>
            <surname>ANNEX VIII - Medical Device</surname>
          </string-name>
          Regulation - medical
          <string-name>
            <surname>-</surname>
          </string-name>
          device-regulation.eu,
          <year>2019</year>
          . URL: https://www.medical
          <article-title>-device-regulation</article-title>
          .eu/
          <year>2019</year>
          /08/08/annex-viii/.
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>MDR</surname>
          </string-name>
          ,
          <string-name>
            <surname>Annex</surname>
            <given-names>II</given-names>
          </string-name>
          (MDR): Technical documentation - de-mdr-ivdr.
          <source>tuvsud.com</source>
          ,
          <year>2004</year>
          . URL: https: //de-mdr
          <article-title>-ivdr.tuvsud.com/Annex-II-Technical-documentation</article-title>
          .html.
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <surname>MDR</surname>
          </string-name>
          ,
          <string-name>
            <surname>Annex</surname>
            <given-names>III</given-names>
          </string-name>
          (
          <article-title>MDR): Technical documentation on post-market surveillance</article-title>
          <string-name>
            <surname>-</surname>
          </string-name>
          de-mdrivdr.tuvsud.com, https://de-mdr
          <article-title>-ivdr.tuvsud.com/Annex-III-Technical-documentation</article-title>
          .html,
          <year>2004</year>
          . URL: https://de-mdr
          <article-title>-ivdr.tuvsud.com/Annex-III-Technical-documentation</article-title>
          .html.
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <surname>MDCG</surname>
          </string-name>
          ,
          <article-title>Guidance on Cybersecurity for medical devices</article-title>
          ,
          <year>2020</year>
          . URL: https://health.ec.europa.eu/ system/files/2022-01/md_cybersecurity_en.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <article-title>NTIA, ntia</article-title>
          .gov,
          <year>2021</year>
          . URL: https://www.ntia.gov/sites/default/files/publications/sbom_related_ eforts_oct2021_
          <fpage>0</fpage>
          .pdf.
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <surname>GDPR</surname>
          </string-name>
          , Art.
          <volume>35</volume>
          <fpage>GDPR</fpage>
          -
          <article-title>Data protection impact assessment - General Data Protection Regulation (GDPR) - gdpr-info</article-title>
          .eu,
          <year>2016</year>
          . URL: https://gdpr-info.eu/art-35-gdpr/.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <surname>FDA</surname>
          </string-name>
          ,
          <article-title>Applying human factors and usability engineering to medical devices, 2016</article-title>
          . URL: https: //www.fda.gov/media/80481/download.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          <source>[27] ISO, IEC 82304-1</source>
          :
          <fpage>2016</fpage>
          -
          <lpage>iso</lpage>
          .org,
          <year>2016</year>
          . URL: https://www.iso.org/standard/59543.html.
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>P.</given-names>
            <surname>Dakić</surname>
          </string-name>
          ,
          <article-title>Software compliance in various industries using ci/cd, dynamic microservices, and containers</article-title>
          ,
          <source>Open Computer Science</source>
          <volume>14</volume>
          (
          <year>2024</year>
          ). doi:
          <volume>10</volume>
          .1515/comp-2024-0013.
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>F.</given-names>
            <surname>Cák</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Dakić</surname>
          </string-name>
          ,
          <article-title>Creating Feature Model for YAML Generator in CI/CD Pipelines with React Web Application</article-title>
          , Springer Nature Singapore,
          <year>2024</year>
          , pp.
          <fpage>529</fpage>
          -
          <lpage>539</lpage>
          . doi:
          <volume>10</volume>
          .1007/
          <fpage>978</fpage>
          -981-97-3305-7_
          <fpage>42</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>P.</given-names>
            <surname>Dakić</surname>
          </string-name>
          ,
          <article-title>Importance of knowledge management for ci/cd and security in autonomous vehicles systems</article-title>
          ,
          <source>JITA - Journal of Information Technology and Applications (Banja Luka) - APEIRON 24</source>
          (
          <year>2024</year>
          ). doi:
          <volume>10</volume>
          .7251/jit2401007d.
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>R.</given-names>
            <surname>Saripalle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Runyan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Russell</surname>
          </string-name>
          ,
          <article-title>Using hl7 fhir to achieve interoperability in patient health record</article-title>
          ,
          <source>Journal of Biomedical Informatics</source>
          <volume>94</volume>
          (
          <year>2019</year>
          )
          <article-title>103188</article-title>
          . doi:
          <volume>10</volume>
          .1016/j.jbi.
          <year>2019</year>
          .
          <volume>103188</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <surname>EU</surname>
          </string-name>
          ,
          <string-name>
            <surname>EU Artificial Intelligence</surname>
          </string-name>
          <article-title>Act | Up-to-date developments and analyses of the EU AI Act - artificialintelligenceact</article-title>
          .eu,
          <year>2024</year>
          . URL: https://artificialintelligenceact.eu/.
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <surname>ISO</surname>
          </string-name>
          , ISO/IEC 27001:2022 -
          <fpage>iso</fpage>
          .org,
          <year>2022</year>
          . URL: https://www.iso.org/standard/27001.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>