This product is an integration platform in a medical institution (a bus). It bridges different supplier platforms together at different levels:
- Plumbing: how to make system A communicate with system B.
- Semantic: what does system A means by this concept versus what system B understands about it and how to create a common ground of understanding.
The platform is a hardware/software combo. It emphasizes the following characteristics:
- Redundant: any failing component can be replaced on the fly without human intervention by one of its siblings.
- Hardware simplicity: the hardware used is abundant but each component is simple. No heavy duty servers with high price tags. We prefer a herd of smaller machines. We refer to them as toasters.
- Distributed: The bus can be extended to several sites as its hardware or several LANs.
- Profile based: Adding a new connexion is done using profiles. If it does not exists for your supplier, we create one. We insist, profile is data, not code added to the product.
- Transmission stubborn: we will not loose data. Even if it kills part of the bus. See the what it's not section.
- Monitored: we know sometimes before you notice it when things might go very wrong. The product does not send sensitive data but it warns us when something seems to be wrong.
- Visible to your staff: you have access to status information, alerts and so on. We do not isolate you from this unless you want to.
- Remotely managed: if we need to act, we need remote access. Sometimes a problem can create more data synchronization issues. We need to fix things before it gets too far.
What it's not:
- A replacement for a failing environment. It's pretty resilient but if your network service is really bad, it will not provide you the top most quality of service. If your power supplier grid is super bad and you do not provisioned for UPS to compensate, there's no miracle that will get you better service.
- An excuse for one of your suppliers to not assume it's support responsibilities. We have a support role, they have one too. We can provide all the necessary proofs to push them back to their duties. But you the customer will loose uptime. We chose the middleman role and it's an uneasy place to be.
- Sexy. Back end products are not sexy. They provide essential services but at some point they are taken as granted after a year after deployment. People forget what it was before this era. That's ok with us.
Sometimes, a department level work-flow is desirable. We can do that. Tap into the data flowing on the bus and provide an extra level of comfort by allowing people to intervene on this data before it gets back on the bus to its final destination. We have one local work-flow for a radiology service and we can create others.
If you need a quality assurance solution we have a minimal one. It's expanding but not certified yet. We are adding modules in the following months to cover many aspects aside from dashboard, document management, internal communication hub, task reporting, defect reports, extended search and so forth that are already available.