Frequently Asked Questions

Questions

1. How will PatientOS meet the needs of clinicians?

1.1. How do you handle the User Interface challenges with any information system?

The entire system user interface is generated from database configuration allowing us to redesign and rebuild the UI as requirements evolve. The hospital will be able to use the same tools to copy a screen layout and make adjustments as needed

Every piece of text visible on the screens can be customized – even the layout of the panels, the depth of the cascading lists, and more.

The interface is consistent throughout the application enabling quick adoption.

1.2. What is PatientOS support for internationalization?

All text displayed throughout the application is stored in the database and can be changed to the language of choice. Some of the application will support multiple languages in the same installation.

Throughout the application the UI can be configured to support different formats for numbers, dates and much more

1.3. How will the implementation team build and configure the application?

Tools to build applications in a near WYSIWYG fashion is available. Most of the build tools follow similar tree structured patterns providing opportunities to automate many functions

1.4. How is the database designed?

The database is designed to be very pure in 3rd normal form with tables strictly representing entities where ever possible.

1.5. How will business rules specific to each facility be implemented?

The JBoss rules engine is integrated with the PatientOS data, business objects and services.

1.6. How will PatientOS integrate with other clinical systems and devices?

The open source Mirth HL7 Integration engine will be leveraged to map HL7 to XML and our business objects

1.7. How will the PatientOS maintain a high standard of quality?

All clinical functionality will be added under strict design control. All changes will be supported by design, requirements and analysis documentation. All clinical requirements will be traced to source code. All source code will be traced to design documentation. Traceability will be maintained as the software evolves.