SFSU_-_iMED_Consent_Description_11-7-16.docx

Santa Fe Service Unit Statement of Work iMed Consent Program, Maintenance and Signature Pads

Purpose of Contract: The Santa Fe Service Unit proposes to implement its RPMS to the iMed Consent System Interface to facilitate passing patient and provider information from RPMS to the IMed Consent at the Santa Fe Service Unit Health Information Management Program.

Background Information: The Santa Fe Service Unit (SFSU) requires a digital accessible signature for services provided at the hospital and outlying clinics. Locations to be included are Santa Fe Indian Hospital, San Felipe Health Clinic, Cochiti Health Clinic and Santa Clara Health Center.

Period of Performance: The interface will be installed and implemented within 90 working days of receipt of the Purchase Order or implementation of the iMed Consent System at the Santa Fe Service Unit, whichever occurs last. The renewal/support will continue to include four (4) option years providing continued to support to the Santa Fe Service Unit.

Estimated Fee Schedule:

Base Year

First Option Year Renewal/Support

Second Option Year Renewal/Support

Third Option Year Renewal/Support

Fourth Option Year Renewal/Suppor

E-padlink/signature pads 24ea/1cs 1ea

A detailed description of the technical requirements.

1) This will be a one-way LL-7 based interface that passes a select set of RPMS patient registration data and RPMS provider data from the site’s RPMS Database to the iMed Consent System. The specific data to be passed is:

2)

a. Patient Data: Name, Health Record Number, Social Security Number, Sex, Date of Birth, Mailing Address

b. Provider Data: Name, Key and Active/Inactive Status Indicator

(Admission, Discharge, Visit, and Clinical Data are not included as part of this interface.)

3) The specified data fields will be passed to iMed Consent for all patients and providers in the site’s RPMS database at the outset of interface operations. This is a one-time activity.

4) On an ongoing basis, data will be passed from RPMS to iMed when a patient is registered or when his or her patient registration data is updated, and when a provider is added to the RPMS system or when his or her information is updated.

5) The software to perform the above functions will be installed and tested by working iMed Consent technical staff. Modifications will be made as necessary and re-tested until the interface performs properly.

6) The interface will be implemented on the site’s RPMS production server.

7) Basic information on operation, troubleshooting and restarting of the interface will be provided by awarded vendor to the local Information Technology staff.

8) The interface will be maintained and supported by the awarded vendor for a period of one-year from implementation at no charge.

9) Requirements of Local RPMS facility and IMed Consent:

a. The awarded vendor will be provided with programmer level access to the site’s RPMS production server and backup/test server (if one exist) for the implementation and support period.

b. iMed Consent technical staff will be available on a timely basis during the development and implementation period.

c. iMed Consent will be responsible for monitoring, troubleshooting and correcting problems that might occur on the iMed Consent side of the interface.

Reference Material.

· iMed Consent for Santa Fe PHS

· 2016 W-9 Taylor Corporation – Standard Register Inc

· ePad VP9801

Deliverables reporting requirements.

· Report and sign in at the front information desk at the main entrance of the facility.

· Report to the Health Information Manager at the Santa Fe Indian Hospital

· Implementation services a project manager works with various staff members for service unit for implementation.