Further Context on the Onesys Navigator (ON)
Scenario: You've just invested in a single EMR instead of a dozen, or an integration platform that allows you for the first time to access information from separate systems. For some reason the problems you set out to solve remain: Doctors and nurses complain about the "clunky" user experience, and they spend more and more time charting.
​
It's time to make your integrated systems navigable with the help of the Onesys Navigator (ON).
​
Described below constitutes patented methods and technologies invented, developed and solely owned by Onesys Medical.
​
Basics
The ON application is executed from the EMR: A simple button or dialogue option will launch the ON software onto a new window, like so:
​
This window is what we call "the Virtual Workspace" - a space for the medical professional to work in. Here's what it looks like after you've launched the program itself:
Legend:
1 = text entry
2 = previous text entries
3 = media zone
This workspace in turn allows the physician to "navigate" to data connected to the ON: The EMR, PACS/DICOM as well as any other HIS-integrated software system or data archive, IoT device or even consumer-generated data buckets are all treated as repositories to pull pertinent information from.
​
Further, saving a workspace creates a specialized file that we call an "ON file", this file can then be exported and and opened with another ON client without the need for a direct datalink. ON files are also viewable from JCOP smartcards.
Here's an example workspace after repeated consults:
Without integration there can be no navigation; Without navigation, information remains difficult to utilize.
​
The problem of the modern digitalized medical information ecosystem is defined not by the quantity or quality of data, but the ease by which it can be accessed and utilized.
We believe that the ON is "the place to put things" that you've been looking for, and the first true solution to the EMR-burnout problem (read here).
​
You might ask: "Time saving as a result of a more efficient system is something we've heard many times - why would Onesys Navigator work where others have failed?"
​
In short: Because it works.
​
With more words: In developing the ON we started out inside of a clinic. We observed clinicians going about their day for extended periods before a single line of code was written. We believe that this effort has given us an inside look into the "invisible obstacles" that others face at the last mile of development.
For us, the customer is the user; for many others, the customer is the healthcare provider. Of course your solution has to meet the demands of both, but we believe that meaningful improvement of the clinical workflow is where the rubber meets the road.
​
If clinicians do not find your solution practical, they will not use it. No matter how hard their employer might push it.
​
A cool thing we've developed recently: We've noticed that MRI machines come with many functionalities: For example, in some systems you can generate volumetric measurements of a tumor with the press of a button. We made it possible to import this data - directly from the MRI system's own software stack - into the ON's media field (pictured earlier).​
​
If you had "a place to put things", what would you put there?
​
As a final aside: The ON's core features are built on proprietary source code. We're open to making this available via SDKs tailored for your needs.
​