* Identify all clinical touchpoints - both on-site and off-site. Touchpoints may be owned, or not-owned.
* Identify all devices capable of DICOM communications.
* Identify all devices capable of HL7 communications.
* Identify all devices and applications capable of PING, PORT, WMI, HTTP, HTTPS, and SFTP which touch the clinical environment.
* Identify assets tied to production, disaster recovery, test, training, and development environments.
* Environments may be on-site, privately hosted, vendor hosted, or a hybrid approach.
* Each environment may be monitored differently with different service levels as well as different notification content and schemes.
* Your existing IT department or IT provider may or may not have extensive monitoring in place. We can identify resources throughout your entire environment and confirm these resources are presently being monitored, and if not ensure they are monitored in the future. In essence, an audit of your existing monitoring approach.
The most common scenario is for 104adt.com to complete a discovery and then supply the monitoring solution. There is a time charge for discovery and then a recurring charge for monitoring which is dependent on the scope of what is being monitored.
It is possible that your IT department or IT provider has software capable of monitoring clinical aspects. In this case we will work with them to augment their current approach. There is a time charge for discovery and to assist.
If you are not ready to implement or augment then we can complete a discovery document and provide it to you for future use. In this case there is a time charge for discovery only.
The best discovery outcome is to prove your existing monitoring has you covered. Below are some more realistic findings:
* Stability issues are not within your data center or hosted environment, but more likely found within your facilities closer to your end-point devices.
* Stability is acceptable for the production environment , but is not adequate for your disaster recovery environment. The general assumption is that the DR environment is 100% ready to go at all times.
* Most monitoring tools install a software agent on Windows devices. This can create problems with clinical software and affect performance. Our solution does not install any agent software.
* Equipment replacements are not always configured correctly resulting in unexpected issues. Equipment may belong to your IT department, a clinical vendor, or an ISP.
* Maintenance activities may be affecting stability. IT planned maintenance, building maintenance, ISP rerouting, or even housekeeping may be affecting uptime.
* Network bandwidth comes and goes, sometimes on a routine schedule. Look to overnight processing and backups as a root cause.
* The gap between what you thought was monitored verses. what is actually being monitored is wider than you thought !
Most all medical disciplines use some type of medical imaging which is based on the DICOM standard.
Most all medical software communicate information via the HL7 standard. HL7 messaging may be behind the curtains, but it is the glue that allows different software applications to share data in real-time.