Clinical data flows, built on knowledge graphs
I'm Marius Conjeaud-Muller, an independent consultant. With HTP42, I help sponsors and CROs deploy OpenStudyBuilder and build graph-based tools that carry study definitions from protocol to submission.
Background
- Since 2013
- Building with graph databases and knowledge graphs, from data modelling to production systems.
- Neo4j Professional Services
- Four years as principal consultant, on customer projects across industries.
- OpenStudyBuilder
- Tech lead, and integrator deploying it for sponsors.
- neomodel
- Lead maintainer of the Python object-graph mapper for Neo4j.
What I work on
Hands-on work, from architecture to delivery, in collaboration with HTP42.
-
OpenStudyBuilder integration
Deploying OSB in your environment and connecting it to the systems around it: installation, hosting and upgrades, integration with EDC, CTMS and metadata repositories, library set-up for your sponsor standards, and training for study builders.
-
Graph-based clinical tools
Custom knowledge graphs on Neo4j for data that is really a network of linked definitions: a clinical metadata repository, impact analysis across studies and standards, graph data modelling and performance, and Python services built with neomodel.
-
Clinical data lineage
Trace every SDTM variable back to the protocol, the CRF and the CDISC standard it comes from, with the lineage held in a knowledge graph so the impact of any change is one query away.
-
Digital protocols and data flow
Turning protocols and study designs into structured data that downstream systems can use: CDISC USDM and ICH M11 readiness, protocol to SDTM trial design domains, controlled terminology management and automated study set-up.
Working daily with CDISC standards
As tech lead of OpenStudyBuilder and an integrator who deploys it for sponsors, I work every day with CDISC standards, USDM and graph-based study metadata.
OpenStudyBuilder is the open-source study definition repository started by Novo Nordisk. It builds structured study specifications that line up with CDISC standards, so the same definition feeds the protocol, data collection and the submission.
Standards and tools I use daily: CDISC Controlled Terminology, SDTM, CDASH, Define-XML, USDM, ICH M11, Neo4j and Python.
Why open source
Open source is a step towards a future worth wanting, where we build together and share what we learn.
I like the spirit of collaboration and collective intelligence that open source makes possible. Clinical research is full of problems that every sponsor solves alone, again and again.
OpenStudyBuilder is part of that change: sponsors, vendors and consultants improving one shared tool instead of rebuilding it behind closed doors. I also maintain neomodel, the Python object-graph mapper for Neo4j, used by OpenStudyBuilder and many other projects.
Other open-source tools I use daily for work and recommend
Let's talk about your project
Pick a topic to open an email, and add a few lines about your context. I usually reply within two business days.
Freelance consultant based near Bordeaux, France, working in English and French.