1.
Preliminary regulatory qualification
Is it a Software as a Medical Device (SaMD)? MDR Rule 2017/745 class I/IIa/IIb/III. Impact: mandatory CE marking, technical file, clinical evaluation, notified body. Advice: have it qualified by a regulatory affairs consultant from the concept phase.
2.
Mandatory HDS hosting
HDS certification (Health Data Hosting) is mandatory as soon as nominative health data is processed. French HDS providers: OVH Healthcare, Scaleway HDS, AWS Paris HDS, Outscale. Structuring choice: includes backup, encryption, SLA, authorized personnel, specific HR agreements.
3.
GDPR and patient consent
Article 9 GDPR: health data equals special category. Reinforced legal basis (explicit consent, care necessity, public interest). Detailed processing register, mandatory DPO, mandatory impact assessment (DPIA) before production, adapted patient legal notices.
4.
Interoperability and standards
FHIR R4 (HL7) equals EU interoperability standard, ANS reference systems (RPPS identifiers for practitioners, INS for patients), DMP (Shared Medical Record) via ANS API, Mon Espace Santé (MSSanté secure messaging), ROR (Operational Resource Directory) for stakeholder geolocation.
5.
Strong authentication and identification
Patients: ProSantéConnect (state SSO), FranceConnect+ possible. Practitioners: CPS (health professional card), mobile e-CPS, RPPS certificate. No simple email plus password account is acceptable for patient record access.
6.
Reinforced security
End-to-end encryption of patient-practitioner messages, encryption at rest of records (KMS HSM), mandatory ANSM pentest for class IIa+ SaMD, annual security audit, ISO 27001 recommended.
7.
Multi-stakeholder architecture
Typically 3-4 roles: patient, practitioner (general practitioner, specialist), care coordinator, adjacent health professional (physiotherapists, nurses). Granular permissions by role and by patient record, access traceability (tamper-proof audit log).
8.
Secure health messaging
MSSante integration (Mailiz, Apicrypt, Lifen) is mandatory for exchanges between health professionals. Workflow: signature, receipt, acknowledgement, 10-year archiving. Technical impact: not a simple SMTP, specific MSSante API.
9.
Telemedicine and reimbursement
If teleconsultation: encrypted video (Tixeo, on-premise Jitsi, Whereby Enterprise), NGAP/CCAM coding, FSE (Electronic Care Form) via SESAM-Vitale, payment and reimbursement by Social Security/CPAM.