The Medical Content team

And product validation

The team

Stina Perdahl

Chief Medical Officer

Åsa Holmgren

Medical Content Software Developer

Christopher Eck Rakovic, MD

Product Owner

Carl Johan Molin, MD, PhD

Medical Quality Compliance & Research Lead

Developers

Britta Söderström, MD

Specialist in Family Medicine

Sanna Siljeholm, MD

Specialist in Family Medicine

Christopher Eck Rakovic, MD

Licensed Physician

Åsa Holmgren

Medical Content Software Developer

Martin Balsvik, MD

Resident Physician in Family Medicine

Petra Jannhans, MD

Licensed Physician

Jesper Gantelius, MD, PhD

Resident Physician in Psychiatry

QA Engineer

Marie-Louise Johansson

What we do

Regulatory and Quality assurance

  • Clinical guidance in Clinical evaluation of all platform24 products
  • Clinical and medical guidance in development risk analyses in all platform24 products
  • In charge of medical incidents and non-conformities in the product
  • Implementation Risk analyses
  • Quality assurance of all medical content

Medical content product

  • Update to latest guidelines based on RGS web
  • Improve the medical content based on input from  clinical evaluation, users and data-analyses
  • Create new medical content 
  • Add search-terms and link to correct questionnaire
  • Recommendation texts
  • Create the short summary of user’s answers to practitioner
  • SelfCare advices 
  • Assessments including healthdata codes
  • Translate and validate the translation of the medical content

Education

  • Educate partners on how the medical content is built and executed
  • Education of partners in how to create medical content in Content24
  • Consult on how to design medical flows

What we do

  • Medical safety and accuracy first
  • Software Development process, according to MDR standards
  • Risk analysis processes
    – development risk analysis
    – implementation risk analysis
  • 4 (-8) eyes principle
    – depending on risk assessment of development
  • Medical specialist sign-off
    Allways external consultants when needed
  • Regression testing/Release-testing
  • Weekly statistic reports/ postmarket surveillance
  • Incident  and non-conformity processes

References used