8 Section III-1. Who is the contact to discuss the arrangement with The selected Offeror will be provided contact information for Temple 4 Part Temple University and the DOC in order to University Hospital upon contract E. 340B meet the 340B requirement of III-1.E 340B Program on Program page 14 of the RFP? 9 Section III-1, At the Pre-proposal Conference held on December 13, Full implementation of the Sapphire EHR will be completed prior to the 4 Part 2016 at SCI-Rockview, the Chief of Clinical execution of a contract resulting from this RFP. D. Information Services at PA Department of Corrections stated that Technology Sapphire EHR is currently functioning as an eMAR and not yet fully functional as an EHR. Since some time has passed, is the EHR referenced in Part III, Section III-1, Part D now functioning as a full EHR? This question is relevant because developing an interface for an EHR and an eMAR are two different tasks. Although the words EHR and eMAR seem to be used interchangeably, the two programs are different. Not knowing the system functionality could cause a delay in the requirement on the first day of the “turnkey” contract start for anyone other than the incumbent.
8 Section III-1. Part E. 340B Program Who is the contact to discuss the arrangement with Temple University and the DOC in order to meet the 340B requirement of III-1.E 340B Program on page 14 of the RFP? The selected Offeror will be provided contact information for Temple University Hospital upon contract 4 9 Section III-1, Part D. Information Technology At the Pre-proposal Conference held on December 13, 2016 at SCI-Rockview, the Chief of Clinical Services at PA Department of Corrections stated that Sapphire EHR is currently functioning as an eMAR and not yet fully functional as an EHR. Since some time has passed, is the EHR referenced in Part III, Section III-1, Part D now functioning as a full EHR? This question is relevant because developing an interface for an EHR and an eMAR are two different tasks. Although the words EHR and eMAR seem to be used interchangeably, the two programs are different. Not knowing the system functionality could cause a delay in the “turnkey” requirement on the first day of the contract start for anyone other than the incumbent. Full implementation of the Sapphire EHR will be completed prior to the execution of a contract resulting from this RFP. 4
Solicitation_28.docx&OriginalFileName=6100041263%20-%20%20Officical%20Questions%20and%20Answers.docx