Proposed in Scope

Functional Scope

• OnCore Enterprise Advarra-Managed infrastructure (AMI)
• Protocols
• Reviews
• Subjects
• Calendars
• Charge Master
• Financials
• Insights (for business intelligence)

Organizational Scope

• UNC-Chapel Hill, including the UNC School of Medicine
• UNC Health Care (partly thru integration with Epic)
• UNC Health Care entities or affiliates (NOTE: These will not treat as individual entities, however; we will develop a process that works consistently for all of them)

Conversion Scope

• Data from UNC’s custom CRMS
• Other systems yet to be identified

Integration Scope

• Epic (for demographic and protocol information)
• IRBIS (for protocol information)
• Peoplesoft (for accounts receivable)
• Shibboleth and Active Directory (for security)
• Possible future integrations:
  • RAMSeS
  • ALICE
  • Florence
  • RedCap
  • Vestigo (for IND/IDE)
  • BoA, Nimblify, GreenPhire (ClinCard) (for patient payments)

Integration with your organization

Text description of flowchart

A complex flowchart graphic with four layers.

• Layer 1: Operational contains two items: Item 1, IRB Systems, interfaces with Layer 3 of the chart via OnCore API. Item 2: Financial Systems interfaces with Layer 3 via the Receivables Interface.
• Layer 2: Products. Contains circles labeled eReg, Payments, and EDC.
• Layer 3: Oncore shows a directional process: Protocol, Reviews, Calendar, Coverage Analysis, Subject Enrollment & Tracking, Sponsor Invoicing, and Reconciliation.
  • The Protocol block interfaces with Layer 1: Operational → IRB System via OnCore API; and Layer 2: Products → Payments via Organizations, Protocols, and Staff.
  • The Reviews block interfaces with Layer 1: Operational → IRB System via OnCore API.
  • The Subject Enrollment & Tracking block interfaces with Layer 2: Products → EDC and Layer 2: Products → Payments via Subject Enrollment.
  • The Sponsor Invoicing block interfaces with Layer 1: Operational → Financial System via Receivables Interface: Invoices.
  • The Reconciliation block interfaces with Layer 1: Operational → Financial System via Receivables Interface: Payments.
• Layer 4 contains a single bubble labeled EHR System. EHR System interfaces:
  • with Layer 3: Oncore → Protocol via Protocol Info (RPE);
  • with Layer 3: Oncore → Coverage Analysis via Billing Calendar Grid (CRPC);
  • with Layer 3: Oncore → Subject Enrollment & Tracking via Demographics and Subject Enrollment (RPE);
  • and with Layer 2: → Products EDC via Labs FHIR.