Reg (EU) 2024/2847Generate dossier — €149
LIVE — Enforcement tracker · Deadline dashboard · Transposition status — Updated weekly from EUR-Lex, Safety Gate, OEIL & 12 official sourcesView regulatory intelligence →

Your Indian healthtech company sells a telemedicine platform to European hospitals. It is not a medical device under Regulation (EU) 2017/745 — so MDR does not apply. But it is a product with digital elements under Article 3(1) of Regulation (EU) 2024/2847. The CRA applies. Article 2(2)(a) exempts medical devices — not health-adjacent software. Your EU hospital client will ask for Annex VII documentation. CRACheck generates it.

Indian healthtech companies selling into Europe face a regulatory gap perception. The team knows MDR (Regulation 2017/745) and assumes that if the product is not a medical device, no EU product regulation applies. Regulation (EU) 2024/2847 closes that gap. Article 2(2)(a) explicitly exempts products covered by Regulation 2017/745 — medical devices. But telemedicine platforms, hospital management systems, wellness apps, and health monitoring tools that are not medical devices remain within CRA scope. European hospital procurement is updating vendor requirements. CRACheck generates 8 PDF documents under Art. 31 + Annex VII in 15–25 minutes. €149 per product. 100% browser-side — patient data never leaves your machine.

Generate Annex VII dossier — €149Free: check if your product is in scope

€149 one-time · 8-document ZIP · 15–25 minutes · Browser-side

Regulation (EU) 2024/2847 · Art. 31 + Annex VII · 8 documents · 100% browser-side — your data never leaves your device

Key numbers

Art. 2(2)(a)
Medical devices (MDR 2017/745) are exempted. Health-adjacent software that is NOT a medical device is NOT exempted.
Annex I §2(e)
Encryption of health data at rest and in transit. Essential cybersecurity requirement.
€149
Per product. Compare with €15,000–€25,000 for a European healthtech compliance consultant.

How it works

1
Confirm your product is not a medical device
If it does not fall under MDR (Regulation 2017/745) or IVDR (Regulation 2017/746), the Article 2(2) exemptions do not apply. The CRA governs your product.
2
Classify under CRA
Use the free CRACheck classifier. Most healthtech platforms are Default category. Products with identity management or access control may be Important Class I (Annex III §1).
3
Complete CRACheck
15–25 minutes. Health-specific inputs: patient data encryption (Annex I Part I §2(e)), access control (§2(d)), data minimisation (§2(g)), secure data erasure (§2(m)).
4
Download the 8-PDF dossier
Structured under Annex VII.
5
Submit to your EU hospital client
Include in vendor assessment response or procurement documentation.
6
Prepare for Art. 14
Vulnerability notification to ENISA from 11 September 2026. Health data breaches are high-visibility incidents.

Three mistakes to avoid

COMMON MISTAKE

"Our product is not a medical device — no EU regulation applies"

Article 2(2)(a) of Regulation (EU) 2024/2847 exempts products covered by MDR (Regulation 2017/745) and IVDR (2017/746). If your product is NOT a medical device, the exemption does NOT apply — and the CRA does apply. Health-adjacent software (telemedicine, wellness, hospital management) that falls outside MDR is squarely within CRA scope.

COMMON MISTAKE

"HIPAA compliance should be enough for EU hospitals"

HIPAA is a US regulation governing protected health information. European hospitals operate under GDPR for data protection and now under Regulation (EU) 2024/2847 for product cybersecurity. HIPAA does not satisfy either. CRA requires product-level Annex VII documentation. GDPR requires data processing records. Neither accepts HIPAA as a substitute.

COMMON MISTAKE

"The hospital is the deployer — they handle compliance, not us"

If you market your telemedicine platform under your brand and sell it to European hospitals, you are the manufacturer under Article 3(1). The hospital is the user. Article 13 manufacturer obligations — including Annex VII technical documentation — fall on you, not on the hospital.

What the ZIP contains

8 PDF documents generated from your data. Each cites the specific article of Regulation (EU) 2024/2847 it complies with.

1

Product Classifier

Classification confirming CRA (not MDR) applies. Important for healthtech products sitting at the boundary.

2

Technical Documentation

Annex VII with health-specific documentation: patient data flows, encryption architecture, access control mechanisms, interoperability with hospital systems.

3

Risk Assessment

Art. 13(2). Healthcare-specific threat model: patient data breach, ransomware, service availability in clinical settings.

4

User Information

Annex II. Hospital IT team documentation: integration requirements, security configuration, data migration, support period.

5

Declaration of Conformity

Art. 28 + Annex V.

6

CVD Policy

Annex I Part II §5. Vulnerability disclosure with healthcare-appropriate response timelines.

7

Notification Template

Art. 14. ENISA notification for healthcare software vulnerabilities. Art. 14(2): early warning within 24h, notification within 72h, final report within 14 days.

8

Obligations Calendar

Key dates.

Mira antes de comprar — Descargar dossier de muestra (PDF, empresa ficticia) — Estructura real, artículos reales, formato real. Datos ficticios.

Generated from your data, in your browser. No data leaves your device.

What you pay

🧾 EUROPEAN HEALTHTECH COMPLIANCE CONSULTANT
€15,000–€25,000
4–6 months. Per product.
✓ CRACHECK
€149
8 documents. 15–25 minutes. Per product.

Two layers of responsibility

● WHAT CRACHECK DOES

Documentation generation

Generates CRA Annex VII documentation for healthtech products that are NOT medical devices. 8 PDFs. 15–25 minutes. €149.

∅ WHAT CRACHECK DOES NOT DO

What falls outside CRACheck

Does not assess whether your product qualifies as a medical device under MDR (Regulation 2017/745). Does not address GDPR or clinical data obligations. Does not replace a health regulatory consultant for MDR classification.

We handle CRA documentation. You handle MDR classification and GDPR compliance separately.

Enforcement regime

Article 64 of Regulation (EU) 2024/2847.

🇪🇺
Non-compliance with Annex I + Art. 13, 14
€15M / 2.5%

Art. 64(2). Health data breaches are the highest-visibility CRA enforcement scenario.

🇪🇺
Missing documentation (Art. 31)
€10M / 2%

Art. 64(3).

🇪🇺
Incorrect information
€5M / 1%

Art. 64(4).

Alternatives

AlternativeCostWhat you get
European healthtech consultant€15,000–€25,000CRA + MDR boundary analysis + documentation. 4–6 months.
Internal team reads the regulationFree + weeks81 pages of legalese. No guarantee of Annex VII compliance.
Assume no EU regulation applies€0Hospital procurement disqualifies your product.
CRACheck€1498 documents. 15–25 min. Healthcare-relevant Annex VII.

Your healthtech has multiple products for EU healthcare?

Telemedicine platform, health monitoring app, hospital management system — each needs its own Annex VII dossier. Contact us for healthtech volume pricing.

Request Volume Pricing
One-business-day response

What CRACheck guarantees and what it does not

CRACheck generates a structured document under Article 31 and Annex VII of Regulation (EU) 2024/2847 from the information you provide. The accuracy is your responsibility as the manufacturer.

We guarantee structure and legal references. We do not guarantee acceptance by a hospital procurement committee or market surveillance authority.

CRACheck is not legal advice. For MDR/CRA boundary classification, consult a qualified health regulatory consultant.

Frequently asked questions

My telemedicine app is not a medical device. Does the CRA still apply?
Yes. Article 2(2)(a) of Regulation (EU) 2024/2847 exempts products covered by MDR (Regulation 2017/745). If your product is NOT a medical device, the exemption does not apply. Your telemedicine app — as a software product with a data connection sold on the EU market — falls within CRA scope under Article 2(1).
How do I know if my product is a medical device or not?
MDR (Regulation 2017/745) Article 2(1) defines a medical device. If your software is intended by the manufacturer for diagnosis, prevention, monitoring, prediction, prognosis, treatment, or alleviation of disease, it may be a medical device. Wellness and operational health IT software typically is not. CRACheck does not make this determination — consult a health regulatory specialist.
Do European hospitals require CRA compliance for software procurement?
Increasingly, yes. Hospital procurement teams in Germany, France, the Netherlands, and Nordic countries are adding Regulation (EU) 2024/2847 compliance to their vendor assessment criteria. Annex VII documentation demonstrates compliance readiness.
Does CRACheck handle GDPR compliance for health data?
No. CRACheck addresses product cybersecurity documentation under the CRA. GDPR compliance — including data processing agreements, DPIAs, and lawful basis for processing health data — is a separate obligation. CRACheck and GDPR compliance are complementary, not substitutes.
Is it a subscription?
No. One-time payment. 30 days editing, 10 regenerations.
Can I request a refund?
Art. 16(m) Directive (EU) 2011/83. Activation = express consent. Refunds only for reproducible technical failures.
What if the regulation changes?
Regenerate at no additional cost during your licence period.
⚠️ Important notice: CRACheck is a self-assessment documentation tool, not legal advice and not a third-party audit. The document under Article 31 and Annex VII of Regulation (EU) 2024/2847 is generated from your input data. You are responsible for the accuracy of the data you provide. CRACheck does not replace a qualified professional assessment.

Your healthtech product is not a medical device — but the CRA applies. Generate Annex VII documentation in 15 minutes.

Eight documents. Annex VII fully structured. Regulation (EU) 2024/2847. Your data stays on your device. The ZIP you download is yours forever.

€149 one-time
8 documents · 15–25 min · No subscription · 100% browser-side
Generate Annex VII dossier — €149
✓ Last regulatory check: 28 April 2026 · No substantive changes detected · View history