7-Attach-C Technical-and-functional-features for-MW26-3-U3P-posting.xlsx

Sheet1

* Proposers need to add their "name" in the designated line above;

* Proposers need to fill in the blanks for each line item in the "Simple Answer" and "Proposer's Explanation / Notes" columns; and

* Some items listed have both a "technical" and a "functional" aspect to them. If this RFP has classified an item as one other the other, Proposer(s) should, in their proposal, still address both functional and technical for that item;

11 = less 99 = Most "Yes";

"No"; or

* For Eligible User(s) subject to Utah's DTS [mostly State of Utah Executive Branch Eligible User(s)], this may be accomplished through federation. If the product or service is accessed or used by both Internal (State employees, contractors, etc.) and External (public, etc.) users, then the product or service must be able to be integrated with multiple identity providers at the same time authentication protocols or direct integration into the vendor-supplied application. Must be able to integrate the State of Utah’s Single Sign-On Entra ID multi-factor authentication using either OIDC or SAML.

* Store all data, as well as any backups made of that data, in encrypted form based on the current TLS standard and include all data as part of a designated backup and recovery process. Encryption of regulatory data must conform with the current regulatory requirement applicable to such data (ex. CJIS, FIPS 140-x)

* Utah State Immunization Information System (USIIS) using HL7 v2.5.1

* Real-time connection via web service "SOAP" or "REST" connection

* Bi-directional interface supporting Z34/Z44 queries and potentially other USIIS specific ones

* Custom MSH-3, MSH-4, MSH-5, and MSH-6 to be assigned by USIIS (UT IIS)

* MSH-11 (Processing ID): Test: doesn’t matter if value is D(evelopment), T(esting) or P(roduction). Production: must be P.

* MSH-12 (Version): Must be included. USIIS accepts: 2.5.1 (no other text)

* "PID-3.5 (Patient Identifier): USIIS requires MR type.

Also support SS and MA types – as repeating identifiers."

* RXA-9 (Administration Notes): Required - send to indicate if facility administered the immunization or whether the facility entered the immunization as part of the patient history. If RXA-9 is blank, USIIS treats immunization as not administered.

"OBX segment – observation types that should be supported by EHR.

-Vaccine funding program eligibility (aka Financial Class), OBX-3: 64994-7 and additional USIIS specific codes -VIS Published Date, OBX-3: 29768-9 -VIS Delivered Date, OBX-3: 29769-7 -Contraindications, OBX-3: 30945-0 -Contraindication Effective Date: 30946-8 -Reactions, OBX-3: 31044-1 -Immunity, OBX-3: 59784-9 -Vaccine Type, OBX-3: 30956-7 -Vaccine funding source: 30963-3"

* Ability to exchange data with immunization information systems through standard HL7 messaging

* Ability to send and receive an electronic laboratory report through standard HL7 messaging

* The user should be able to add and remove items from the list;

* Items on the list should be marked with a configurable acuity level (chronic vs acute) for each problem/diagnosis;

* Problems/diagnoses should also have a configurable expiration date, for example in the case of pregnancy;

* Treatments/tasks/medications/clinical encounters should be linkable to these problems/diagnoses; and

* For Eligible User(s) subject to Utah's DTS [mostly State of Utah Executive Branch Eligible User(s)], if there is use of generative Artificial Intelligence (“AI”) in the product or service, comply with DTS POLICY 4000-0008 Enterprise Generative AI Policy and conform with the current regulatory requirement applicable to such data (ex. CJIS, FIPS 140-x)

* For Eligible User(s) subject to Utah's DTS [mostly State of Utah Executive Branch Eligible User(s)], all data is owned by the State of Utah and use of the data outside the scope of this project requires prior authorization.

i. Maintains unique name and/or number for identifying and tracking user identity

ii. Ability to set permissions/security by user or role classification

iii. Supports various levels of administrator-assigned user rights

iv. User management process allows authorized users to generate, modify, and delete user accounts

The Eligible Users need an EHR that has the ability to allow for the correction of information that has been entered into the chart in error.

* There needs to be an ability to “move” data that was entered into the incorrect patient chart to the correct patient chart;

* There needs to be an ability to edit or delete data in a patient chart; and

* EHR that comes with standard pre-loaded orders for vital signs, blood glucose checks, standard labs, radiographic exams, etc.;

* Orders separable into groups such as radiology, lab, nursing treatments, provider visits, etc. (with the ability to customize these groups);

* Orders have configurable frequencies (once a day, before meals etc.);

* Order duration for repeating orders also configurable by days, weeks, months, years or continuous (repeating until patient is discharged);

* EHR has the ability to create custom orders and order sets; and

* Order entry needs to be streamlined and allow for input of multiple orders with the same provider, date, etc. without re-specifying for each individual order. (For example: a provider being able to order 4 labs all at once without having to put the date and provider name on each of the 4 labs individually)

* For example, if an RN determines while completing a screening form generated in the EHR that a patient is diabetic, and signifies this on the form, a predetermined set of orders must be possible such as: a diet order, blood glucose check orders, physician referral, etc.;

* Orders or order sets need to be configurable by cell location. For example, patients housed in segregation cells could have an automatic daily segregation check task placed into the nursing tasks queue; and

* EHR pre-loaded with a list of common allergies;

* User(s) have the ability to add custom allergies, including non-medication allergies;

* User(s) have the ability to remove allergies from the list when an allergy is removed, the EHR presents a prompt requiring the user to provide the reason why the allergy is being removed;

* Tasks need to be assignable to a specific user, user group, or class;

* Users, groups, and classes must have the ability to open/view a queue of uncompleted tasks; and

* Data entry fields customizable by task; and

* For tasks that have been configured to require MD/Provider sign off, completion of the task will place it, along with the entered data/result, into an MD/Provider queue for disposition/signoff.

* In the case of order “sets” (for example: "5 days of blood pressure checks" or "7 days of blood glucose checks"), these tasks will not appear for MD signoff until the entire set is completed and ready for review;

* From this queue the clinician will have easy access to historical results of the same order type so they can watch for trends;

* These tasks may be assigned to a specific MD/Provider or to group queues, depending on the task;

* The queue of tasks will allow for easy signoff of multiple items in a batch format; and

* Forms utilize as many interactive and time saving devices as possible, for example: check boxes; radio buttons; drop down lists; decision trees; tables; free-text (with spell checking); scanned documents; etc.

* Based on information provided in these forms, the EHR will allow for the triggering of automated actions (workflows) such as outlined in the orders and order sets section in this document.

* Patient based communication will indicate whether or not said communication has been read or not read;

* Patient based commination will allow for digital signature of communications;

* The EHR needs to have the ability to manually create a patient chart in the EHR in case the interface with the OMS is temporarily unavailable. Once the interface is restored, a report must be automatically generated that shows discrepancies, if any, between manual entry and the interface. These discrepancies must have the ability to be resolved by the Eligible User's on-site administrator.

* The interface must reconcile all data displayed in both systems at a minimum of a 24 hour interval. A report must be automatically generated that shows discrepancies, if any. These discrepancies must have the ability to be resolved by the Eligible User's on-site administrator.

* The interface with the contracted Pharmacy must use HL7 and include: Demographic information; Last name; First name; Middle name; Date of birth; Gender; Medical record number (Eligible User's number); Bookings (admission); Roll-up (discharge); Cell location (movement); Allergies; New prescription orders; Changes in prescriptions; Discontinuation of prescriptions

* Changes made in either system must be updated to both systems at a minimum of 15 minute intervals.

* The EHR needs to have the ability to manually print out prescriptions so that they can be faxed to the pharmacy if the electronic interface become unavailable.

* Once the interface is restored, a report must be automatically generated that shows any discrepancies between manual entry and the interface. These discrepancies must have the ability to be resolved by the Eligible User's on-site administrator.

* View "PRISM Companion Guides" at https://medicaid.utah.gov/hipaa/providers/#companion-guides

* https://medicaid.utah.gov/hipaa/providers/#companion-guides

* Medications searchable by both generic and brand names;

* Medication order template(s) require the linking of a patient specific diagnosis to the medication order;

* Medication order template(s) require the selection of an ordering prescriber and if the ordering prescriber is not the active user, this medication order gets electronically submitted to a queue for signoff by the ordering provider;

* Medication order template(s) are pre-loaded (common frequencies, routes, dosages, etc.) and the user has the ability to customize any of these fields;

* Medication order template(s) are able to note "required" medications (for example: board-ordered meds that can have consequences if the meds are refused);

* Medication order template(s) allow for easy titrating of medications; and

* Configurable renewal reports (for example, the ability to run a report for medications expiring in “X” number of days);

* Automatically-generated renewal request(s) go into an electronic queue so that the ordering provider(s) can easily disposition these requests;

* EHR has the ability to automatically and electronically submit refill order(s) to the Eligible User's pharmacy vendor for active prescriptions; and