It is the infrastructure layer underneath the clinical applications: it reads continuously from the monitors and the EMR your hospital already runs, stores what they produce in a usable structure, and makes it visible and annotatable for your own teams. Most hospitals already generate this data and then lose it at the bedside. The platform is what turns it into something you can look at, research on and run algorithms against.

A warehouse stores what has already been written to the record, and it serves secondary use: research, analytics and quality reporting on data after the fact. The Intellicens Data Platform is built for primary reuse, putting the same data back to work for the patient it was recorded on, during the same admission. That is the same split the European Health Data Space draws between primary and secondary use of health data. In practice it reads continuously from the monitors and the EMR, captures the signals that normally never reach the record at all, keeps them as one continuous record over the whole admission, and lets clinicians annotate them while they are still reviewing the patient. It also runs inside the hospital perimeter and inside an ISO 13485 quality system, so an algorithm developed on it has a route to CE marking under MDR and to a 510(k) submission instead of staying a research project.

Four things. First, it is built for primary reuse: the data comes back to the patient it was recorded on, during the same admission, instead of waiting in an archive for research that may happen next year. Second, it is built by the clinicians who use it rather than specified from the outside, and that shows in the usability: a team builds and changes its own dashboards in the browser instead of filing a request with a vendor. Third, it carries a catalogue of clinical applications, seven of them in the pipeline today, developed by Innocens and by academic partners and all running on the same installation, starting with Intellicens Neo for late-onset sepsis in the NICU. And fourth, it runs on-premise, so patient data never leaves your perimeter.

No. Nothing at the bedside changes and no existing system is swapped out. Intellicens reads from the monitors and the electronic medical record you already run, over the HL7 and FHIR interfaces your hospital already operates, and it never alters or replaces the primary monitor. It runs alongside your current stack on your own servers, so the decision is additive rather than a migration.

It is sensor-agnostic. Bedside monitors from vendors such as Philips, Dräger and GE are read over HL7, and context from the electronic medical record comes in over FHIR, using interfaces your hospital already runs. No new hardware is added at the bedside and the primary monitor is never altered or replaced.

On your own infrastructure, on-premise or in your private cloud. Patient data does not leave your perimeter. Your institution keeps ownership of its data in an accessible and extractable form, access runs through your identity provider and role model, and every view and export is logged. Modules and updates are deployed in containers on-site, so the network perimeter does not need to be opened.

Visualize continuous signals across the whole admission, annotate events, build cohorts, and use that data for retrospective research and feasibility work on new clinical questions. The same capture and annotation tooling is what a model is later validated on, and what puts it within reach of the catalogue of applications running on the platform.

Intellicens Data Platform is investigational medical device software. It is not CE marked under EU MDR 2017/745, it has not been cleared by the U.S. Food and Drug Administration, and it is not available for commercial clinical use. The clinical applications that provide decision support are the regulated part, and they follow the conformity assessment route under EU MDR 2017/745 with BSI as notified body. The platform is the infrastructure they are built and deployed on, developed inside the same ISO 13485 quality management system, so an application inherits that base instead of starting a standalone dossier.

Yes. Validating a model against live primary data in a running unit is exactly what this layer exists for: the same pipeline that carries the applications in the catalogue carries yours, and every step is documented for the regulatory file, so a model that proves itself has somewhere to go instead of stopping at a publication. Ownership and revenue sharing are agreed in writing per case, before development starts. The shape of that agreement is deliberately left open, because it is negotiable and it should follow what each side actually brings.

Yes. What you add is deployment and evidence: the same on-premise stack the platform already uses, the sensor and EMR connectors, the on-site installation and the training clinical teams expect. Real-world evidence is then generated continuously from the sites where it runs, which is usually the hardest part to arrange alone.

On-premise servers or a private cloud environment, the HL7 and FHIR interfaces your hospital already operates, and a data governance agreement with your data protection officer. Installation, connector configuration and training are done on-site. Once the platform is in place, adding applications is a configuration step rather than a new project.