Medical software ready for audit
We help medical device manufacturers and pharmaceutical companies get their software ready for regulatory requirements. The whole agreed scope is covered by one contract.
Compliance costs the most when it comes too late
Regulatory requirements affect many areas. The architecture, the way the software works, or its testing. If we only take them into account at the end, the changes can turn out to be very costly. Why not take care of this area earlier? We suggest analyzing requirements and risk at the start of the project.
In medical software, patient safety and cybersecurity are linked. A function needed in an emergency may call for a special approach to access control.
We analyze these dependencies while designing the software. We take patient safety and personal data protection requirements into account, so every technical decision is backed by the requirements and the risk assessment.
Six areas we run in one process
You can entrust us with a selected part of the work or combine several services into one project. We design software to meet the requirements of the EU Medical Device Regulation (MDR) and the guidance of the US FDA. We set the exact scope based on your product's stage of development and other materials.
- Appotype
Cybersecurity compliant with MDR and FDA
We prepare the threat model and the cybersecurity risk analysis. We also write the documentation that shows how the project addresses these risks.
- Appotype
Bringing a device from MDD to MDR
We review your existing documentation and point out what needs to be completed. Based on that, we plan the work of bringing the device in line with the MDR.
- Appotype
Design and regulatory documentation
We write the documentation while we build the software. You get a consistent set of materials you can use in an audit.
- Appotype with a partner
Regulatory consulting
We help turn regulatory requirements into concrete project tasks and work out how they affect the architecture, the documentation and the way the software is verified.
- Appotype with a partner
Quality management system (QMS)
A consulting partner helps you put quality procedures and processes in place. We build the software in line with the agreed rules.
- Appotype with a partner
Preparing for an ISO audit
A consulting partner prepares your organization for the audit, and Appotype provides the materials on the software. The certificate is issued by an independent certification body.
Cybersecurity for MDR and FDA in one process
Bringing medical software to the EU and US markets means reconciling two regulatory systems. Instead of running separate certification tracks, we combine threat modeling, risk assessment and documentation into one consistent engineering process.
Threat modeling from day one
We identify potential attack vectors as early as the architecture design. Mapping threats early lets us build defenses straight into the software code.
Risk assessment: security and safety
We give every identified threat the attention it deserves. We clearly separate the protection of infrastructure and data from direct impact on patient health. We put technical controls in place that effectively mitigate both types of risk.
Documentation ready for review
Every architectural decision leaves a trace. We build a clear traceability matrix that links theoretical risks directly to specific tests and written code. We hand you audit-ready evidence.
Documentation your team can work with
We prepare documentation that fits your product's requirements and the project scope. Each document has a clear role.
You can also rely on it in later stages of product development, in audits and when working with other contractors.
Software requirements specification (SRS)
Defines what the system does, the conditions it runs in and the requirements that have to be verified.
Software development plan (SDP)
Describes the stages of work, responsibilities and procedures used while developing the software.
Software architecture
Shows the structure of the system and the reasoning behind key technical decisions.
Test plan
Defines how the software is verified and traces each test to its requirements.
Threat model
Sets out possible attack scenarios and the areas that need further assessment.
Cybersecurity risk analysis
Assesses the threats identified and describes the measures that reduce the related risk.
App mockups
Show the structure of the interface and how the functions described in the documentation are used.
One contract and clear roles
One point of contact
You sign the contract with Appotype. We coordinate the agreed scope of work and handle the billing for the whole process.
The right expertise for each area
We assign each task in the project to people with the right qualifications.
Responsibilities set from the start
Before we start working together, we agree on the scope of tasks, the responsibilities and how the teams communicate.
Let's talk about your project's requirements
At the first meeting, we discuss your product, its stage of development and the requirements it has to meet. If you already have documentation, we can start by reviewing it and pointing out what needs to be completed.
Questions and answers
See how we can support your team and which areas we take responsibility for.
Can we order compliance support without hiring you to build the software?
Yes. We can work alongside your development team and take responsibility for the agreed scope of documentation, risk analysis and cybersecurity. We fit the way we work to your existing software development process.
Do you support cybersecurity compliant with the MDR and FDA requirements?
Yes. For a Polish medical device manufacturer, we prepared the threat model, the cybersecurity risk analysis and materials for the device's security documentation. We also handle MDR and FDA requirements in one process. A guide co-written by the CEO of Appotype is devoted to this approach.
Who is responsible for the quality system and the ISO audit?
Our consulting partner handles this area. Appotype coordinates the work under the agreed contract and is responsible for the software part. Certification is carried out by an independent certification body.
What materials do we get if we order documentation only?
It depends on the product and its requirements. The scope may include the requirements specification, the software development plan, the architecture description, the test plan, the threat model, the risk analysis and mockups. We hand over the materials with the agreed rights to use them further.
Our device was built under the MDD. Where do we start adapting it to the MDR?
We start with a review of the existing documentation. That shows what needs to be completed and lets us plan the next steps. After our call, we prepare a quote for the review.
Do we need our own regulatory team?
It is not a condition for working together. We can help you organize the requirements and work out how they affect the software project. In regulatory and quality areas, we work with a consulting partner.







