Medical Ltd
Headquarters: Slovenia
Size: 1 - 10 employees
Trading since: 2021
Membership level: Startup partner
Mapping Legacy EHR Data to openEHR
Legacy EHR data migration to openEHR with YAML mapping and with an interpretable programming language for data transformation inside YAML.
Executable Clinical Pathways
The plan is to test if BPMN can be used for modeling and executing clinical pathways.
I was told by a few knowledgeable persons that modeling clinical pathways is too complex. I believe them but that doesn't mean we shouldn't try to model at least some of them. I’ll see how much I can contribute to these efforts.
Generate Anything
openEHR specifications are detailed but also complex. Why risk introducing bugs while converting them into code? Why not generate as much code as possible?
Many things can be generated from openEHR specifications:
- Forms - complete mobile/web applications used for entering data into an openEHR system
- OPT2 SDK - model classes for working with openEHR data
- GraphQL - schemas, server and client from operational templates
- OpenAPI - definitions for openEHR models
- Diagrams - UML diagrams for openEHR models
Products
| Name | Description | Product type | ||
|---|---|---|---|---|
| MapEHR | Legacy EHR data migration to openEHR with YAML mapping with full OO programming language for data transformation inside YAML. |
EHR Platform | ||
| MedicalFlows - Executable Clinical Pathways | Orchestrating executable medical workflows with support for openEHR CDR. Clinical pathways, clinical guidelines, clinical protocols, clinical workflows, clinical best practices, task planning, care coordination plans, care pathways, nursing care plans, clinical process modeling, medical process modeling, healthcare practice patterns, plans and decision logic, process and reasoning models,... There are so many different names to describe what these diagrams represent - I call them Medical Flows.
|
CDS | ||
| MedicalFlows - Modeler | Modeling tool for creating executable medical workflows with support for openEHR CDR. Clinical pathways, clinical guidelines, clinical protocols, clinical workflows, clinical best practices, task planning, care coordination plans, care pathways, nursing care plans, clinical process modeling, medical process modeling, healthcare practice patterns, plans and decision logic, process and reasoning models,... There are so many different names to describe what these diagrams represent - I call them Medical Flows.
|
Modelling Tool | ||
| MedicalFlows - Workflows | Orchestrating executable medical workflows with support for openEHR CDR. Clinical pathways, clinical guidelines, clinical protocols, clinical workflows, clinical best practices, task planning, care coordination plans, care pathways, nursing care plans, clinical process modeling, medical process modeling, healthcare practice patterns, plans and decision logic, process and reasoning models,... There are so many different names to describe what these diagrams represent - I call them Medical Flows.
|
EHR Platform | ||
| openEHR Forms | Select operational templates you wish to use in the same application. Click generate. Wait 10 seconds. Your application is ready. It is a Flutter app that runs on:
When you change your templates or there is a new releases of major archetypes, you re-run the generator and few seconds later, your applications and forms are rebuilt and ready to use. With NeoEHR, you will get results faster, eliminate usage fees, retain high customization capabilities and full control over the codebase of your solution.
|
EHR Platform | ||
| SDK for Operational Templates | The idea is to have native classes that can be used by developers without requiring them to know anything about openEHR. Instead of giving them the OpenAPI schema and asking them to send data to the openEHR CDR, let them use simple classes in their favorite programming language they are used to work with. These classes (SDK) take care of everything openEHR related and can be used in “frontend” languages that web developers are familiar with.
|
Library |
