Analytics Engine
Treatment effects from routine data. Methods for histories with uneven intervals and changing treatment.
MedRecords holds diagnoses, procedures, medications, lab values, free text and everything else as entities on the patient, each with its date. When a new type appears, a node is added: no schema to extend, no data to migrate. Every product in the portfolio works with this data container.
Events hang off the patient, each with its date. Where the data source carries encounters, cases or stays, they are represented as a separate level. The model prescribes no intermediate level and loses none either. Point at an entry to see all entries from the same day.
Schematic view of an excerpt. Further entity types are possible.
A MedRecord is a unit that can be serialised, passed on and loaded directly into a model. No database that first has to be set up and connected.
What lies between two events, how large the intervals are, in which order something happened: that follows from the structure itself, rather than being reconstructed through sorting and nested queries.
Each event type carries the attributes it has. A medication needs dose and active substance, a lab value needs unit and reference range. There is no common row width that everything must conform to.
Included in the repository, open source, free to use.
Treatment effects from routine data. Methods for histories with uneven intervals and changing treatment.
Selection by the order of and distance between events, not just by codes inside a time window.
Every transformation is recorded, so a result can be traced back to the raw data.
OMOP tables, CSV and Parquet are read in without having to be forced into a grid first.
Extensions for running it in house, with support and ongoing development.
Reads FHIR resources and writes results back, both directions over the same MedRecord.
Maps in-house and regional codings back to OMOP vocabularies, with a record of each assignment.
MedRecords works directly on existing systems, so no second copy of the data appears.
Pre-trained vector representations for all OMOP vocabularies, ready to use in your own models.
The source code is public. What the code does can be checked by your IT and your data protection officer too, before the first installation.
MedRecords on GitHubMedRecords is the medical application of a general graph library. GraphRecords itself knows nothing about medicine, only nodes, edges and attributes.
Go to the GraphRecords pageWhether an import is worth it depends on your data sources and catalogues. A first conversation usually settles that quickly.