There are three possible levels of integration between OnCore and eRecord:
- ADT – When a subject is registered in OnCore with their eMRN, patient demographic information is pulled into OnCore from eRecord. Once this connect is made, both patient enrollment and study information will be available on the Research Tab in eRecord.
-
- Local MRNs (also called Dummy MRNs) can be used in a variety of situations to stop the linking of subject demographic information across OnCore and eRecord.
- Local MRNs cannot be used in studies with billing risk, that use MyChart for Recruitment or other eRecord research functionality; study information by default will be included in the patient’s chart.
- RPE – The OCR team in collaboration with Research Compliance sends all billing risk studies from OnCore to eRecord via the RPE interface. All Studies using MyChart for Recruitment will also use this interface. Non billing risk studies may be sent on a case by case basis (for example a patient safety reason). The RPE push sends both summary-level protocol information and basic subject information including:
- Protocol identifiers (Protocol No., NCT Number, IRB No.)
- Staff (PI, Protocol Staff)
- Protocol descriptors (Short Title, Protocol Type)
- Arm data (Protocol Arm Code)
- Subject status information (associated protocol identifier, subject status, relevant dates, sequence number).
- CRPC – Sends billing grid information to eRecord including study-related relative time points with associated Charge Master events. This functionality has been used in the past but is not actively being used as of January 2024.
Per the Research Subjects Review Board:
All studies that will document information regarding study participation in eRecord/MyChart, including the documentation of any/all information pushed into eRecord/MyChart from OnCore, must disclose this via the consent process. Consent forms, including verbal consent scripts and information sheets (as appropriate) must include the RSRB’s eRecord/MyChart template language. Please see RSRB Consent Templates and/or contact your IRB Coordinator with questions.
If there is a compelling reason why you believe your study should not use the OnCore-eRecord integrations (e.g. use of local MRNs for caregivers and guardians), this information should be documented in your study protocol and you will need to consult with:
- Mike Ritz to ensure billing compliance
- OCR to ensure your study is set up correctly to disable the integration
- IRB as they may also require documentation in the subjects’ health records for their safety, which is different than the automated integration.
After consultation with the 3 parties listed above, if your study is approved to not use the OnCore-eRecord interface, then you can work on your consent language with your IRB specialists as eRecord documentation language may not be required in the consent form(s).
Please note: Even for studies that do not use the OnCore-eRecord integration, it is entirely possible that patients may disclose participation in a trial to a provider, and that provider may deem it necessary to document participation in eRecord.
Please reach out to the OCR with any questions about OnCore (Clinical_Research@URMC.Rochester.edu).