MediReady.
CLASSIFICATION & READINESS

MediReady — Swedish Market Classification & Readiness Document

Assessment: not medical device software (MDSW) and not a national medical information system (NMI). Fully aligned with Swedish regulatory expectations for administrative compliance tools.

Version: 2.0
Date: 2026-05-24
Prepared by: MediReady AB

Table of contents

  1. Purpose
  2. Product Description
  3. Intended Purpose
  4. Assessment under MDR (EU 2017/745)
  5. Assessment under HSLF-FS 2022:42 (National Medical Information Systems)
  6. Swedish Regulatory Framework Context
  7. Data Protection and GDPR
  8. Swedish Data Protection Authority (IMY) Alignment
  9. NIS2 Directive — Scope and Applicability
  10. European Health Data Space (EHDS) — Future Monitoring
  11. Data Residency and Geographic Processing
  12. Overall Conclusion

1. Purpose

This document establishes MediReady's formal classification and regulatory readiness for the Swedish market in relation to:

The document describes MediReady's intended use, functional limitations, and regulatory boundaries as the basis for the assessment that the product is not within the scope of MDR and not within the scope of the NMI framework, while remaining fully aligned with Swedish data protection expectations.

2. Product Description

MediReady is an administrative tool for compliance documentation and workflow audit. The system is used by administrators, quality leads, and operations managers to:

MediReady does not process medical decisions, does not influence patient care, and does not provide recommendations on diagnosis, treatment, or clinical actions.

3. Intended Purpose

MediReady is intended for:

MediReady is not intended to:

4. Assessment under MDR (EU 2017/745)

4.1 Relevant Criteria

Under MDR, software is classified as a medical device if it has a medical purpose, for example to:

4.2 Assessment

MediReady meets none of MDR's medical purposes. The system:

“Software for administrative purposes is not covered.” — MDR interpretation per EU guidance

4.3 Conclusion

MediReady is not a medical device and is not within the scope of MDR.

5. Assessment under HSLF-FS 2022:42 (National Medical Information Systems)

5.1 Relevant Criteria

NMI covers systems that:

5.2 Exception in the Regulation

HSLF-FS 2022:42 states that the following is not NMI:

“Generic software used in a care environment, except where the software has been adapted in a way that meets the definition of a national medical information system.”

5.3 Assessment

MediReady:

5.4 Conclusion

MediReady does not meet the definition of NMI and is not within the scope of HSLF-FS 2022:42.

6. Swedish Regulatory Framework Context

MediReady operates in Sweden under the following regulatory framework:

RegulationReferenceRelevance
GDPREU 2016/679Data protection framework
Patientdatalagen2008:355Swedish patient data law
HSLF-FS 2022:42Swedish National Board of Health and WelfareRegulations on national medical information systems (NMI)
MDREU 2017/745EU medical device regulations (applicable in Sweden)
IMY Supervisory PracticesIntegritetsskyddsmyndighetenSwedish DPA guidance on AI, healthcare, and sensitive data

Critical classification question for Swedish healthcare providers: Is MediReady a medical device (MDSW) or a national medical information system (NMI)?

The answer is no to both. MediReady is subject to GDPR but not to medical device or NMI-specific regulations.

7. Data Protection and GDPR

Even though MediReady is neither MDSW nor NMI, the system is subject to GDPR.

AspectMediReady Commitment
Data processingInputs are processed ephemerally in memory and discarded immediately
Data storageNo PHI is stored; stateless architecture
CollectionNo background collection, telemetry, or profiling
ControllerThe healthcare provider is the controller
ProcessorMediReady is the processor
AgreementA data processing agreement under Article 28 is required (provided separately)

8. Swedish Data Protection Authority (IMY) Alignment

IMY (Integritetsskyddsmyndigheten) has published supervisory priorities for 2024–2025 that include:

MediReady's design aligns with IMY priorities as follows:

8.1 AI Transparency

RequirementMediReady Commitment
Model disclosureMistral Large LLM with signed BAA (no training use)
Human oversightCritical findings reviewed by qualified auditors
Input deletionStateless processing eliminates data retention risk

8.2 Sensitive Data Minimization

AspectMediReady Position
Data typeAdministrative data only, not patient medical records or PHI
GDPR Article 9No categorization under special categories in normal use
Incidental sensitive dataStateless architecture and immediate deletion mitigate risk

8.3 Data Subject Rights

MediReady assists the Company in responding to Data Subject Access Requests (DSAR) and other rights under GDPR Articles 12–22. (See §6 of the Data Processing Agreement.)

8.4 Accountability Documentation

MediReady maintains:

Documentation is made available to IMY upon inspection request.

8.5 Commitment to Swedish Law

ElementCommitment
Governing lawAll disputes and legal questions governed by Swedish law
DPA jurisdictionSwedish governing law and jurisdiction

9. NIS2 Directive — Scope and Applicability

The EU NIS2 Directive (2022/2555) sets cybersecurity obligations for critical infrastructure operators and essential service providers.

9.1 When NIS2 Applies

NIS2 applies where a company:

9.2 MediReady's Position

QuestionAnswer
Is MediReady automatically in scope for NIS2?No
Why?Not an EHR system; does not maintain national health-data infrastructure; does not directly deliver healthcare services

9.3 Important Note for Swedish Healthcare Providers

If MediReady is used by a Swedish healthcare provider (e.g., region, clinic, hospital) that is itself a NIS2 essential actor, that provider's NIS2 obligations may extend to evaluating MediReady's security posture as part of their supply-chain risk management.

9.4 MediReady's NIS2 Commitments

RequirementMediReady Commitment
Security measuresComply with NIST Cybersecurity Framework (CSF) principles
Incident reportingAlign with NIS2 reporting timelines (72-hour breach notification)
DocumentationAvailable upon request for healthcare providers' NIS2 compliance assessment

10. European Health Data Space (EHDS) — Future Monitoring

The EHDS Regulation (2023/2664) is under implementation.

10.1 What EHDS Addresses

10.2 MediReady's Position

QuestionAnswer
Is EHDS currently applicable to MediReady?No
Why?Applies to EHR systems and national data-sharing infrastructure, not compliance-audit tools

10.3 Monitoring Commitment

MediReady:

10.4 EHDS Implementation Timeline

PhaseTimelinePrimary Focus
Phase 12025–2026EHR interoperability
Phase 22027+Secondary use and data-sharing frameworks

MediReady evaluation timeline: Q1–Q2 2026

11. Data Residency and Geographic Processing

MediReady Guarantee

CommitmentDetail
Processing locationAll processing of Company Personal Data occurs within the European Economic Area (EEA)
Inference locationMistral AI occurs within EU data centers
Non-EEA transferNo non-EEA data transfer without explicit Company written consent
Restricted jurisdictionsNo data transferred to the United States, Asia, or any non-EEA jurisdiction

This commitment applies to all Company Personal Data, including administrative records, policies, and workflow documentation provided to MediReady.

12. Overall Conclusion

Based on intended use, functionality, and regulatory criteria, MediReady is assessed as follows:

Regulatory AreaStatus
Medical device (MDSW) under MDR (EU 2017/745)✓ Not a medical device
National medical information system (NMI) under HSLF-FS 2022:42✓ Not an NMI
NIS2 Directive automatic scope✓ Not in automatic scope
EHDS current scope✓ Not in current scope
GDPR and Swedish data protection law✓ Subject to
Patientdatalagen (2008:355)✓ Aligned with
IMY supervisory authority✓ Subject to
Swedish data-protection expectations for healthcare software✓ Aligned with

For Swedish Healthcare Providers

You can use MediReady as an administrative compliance and workflow tool. You must:

The tool does not substitute for legal or clinical counsel.

Prepared by: MediReady AB
Version: 2.0
Date: 2026-05-24

End of document