How does the system lend itself to automated back-ups? Does the vendor provide IT support team to implement specific back-up plans that will work with the hospital's IT team?.
Is the software capable of using biometric data for rapid login by providers who are mobile between patients/sites?.
How does the system handle user inactivity? (auto-logout, discarding\saving changes, draft creation).
How does the system handle multiple logins of the same user at different locations/instances?.
Is the system using standards such as Snomed, ICD 10 HL7 Version 2 or 3 HL7 infobutton…).
Is the vendor’s application (system) platform independent?.
#Another word for selection criteria Patch#
How frequently does the vendor provide patch upgrades for the product?.
Does the system provide an imaging database or allow customized program attachments of imaging needs of specific departments in the hospital?.
Does the system use DICOM standards for the transmission of image data?.
Will technical support remain active even if the Hospital is running a non-upgraded system? For how long?.
How the vendor estimates the total amount of users and licenses needed? Will they be concurrent user licenses or asynchronic?.
For already existing software functionality, does the vendor employ reliable and trustworthy software like an open-source MySQL or Apache server? Or do they develop their own system, or do we have to license a proprietary one (extra cost)?.
2.6 Management and Reporting Requirements.
2.5.1 Continuity of Care: Outpatient vs Inpatient EMR.
1.6 Health information exchange, connectivity, and standards.