At Minnesota, the cancer center had OnCore prior to going enterprize wide with it. At the time the cancer center used it initially, OnCore did not have the potential for integrating data with Epic.
Currently, most data capture for clinical trials is done using case report forms in Oncore - rather than Epic For BMT - there are smart forms and templated notes built in Epic at point of care with the goal to flow data from Epic to Clarity to the cancer center database. This has been a 2 year project and reports of the data are not yet available. Changing the Epic build for an RCT protocol may not be the highest priority for the health system, given all the clinical documentation issues they need to address. Building structured notes or flowsheets may be doable, but then it requires an Epic builder. If the data are not part of routine required data, then it still will require research staff to enter the data. It may be easier to build a PCORI database initially. Beacon - now includes staging and staging data should be capture in Epic going forward, now can that data be in Clarity and AHC-IE Josh, our CTMS project manager notes that the CTMS Implementation roadmap includes some data integration with EPIC based on a combination of need and technical capabilities. The integration items at a high level include: Demographic data pulled from EPIC to OnCore for registering clinical trial subjects, sending basic protocol information to EPIC, sending basic subject data to EPIC to indicate that subject is on a specific protocol and sending the OnCore billing grid to EPIC. The capability does exist, and was successfully tested when working at the Masonic Cancer Center, for us to also bring in lab data from HL7 data sources into OnCore electronic case report forms. This functionality is not currently on the CTMS Implementation roadmap. Fairview has trained some staff in research on setting up the basic research "protocol" components in EPIC which will be needed for the OnCore integration to work. The OnCore vendor has been working on plans to expand the EPIC integration capabilities. Yale is leading the way on much of this work. I hope to learn more during the conference this week. Bonnie L. Westra, PhD, RN, FAAN, FACMI Associate Professor, University of Minnesota, School of Nursing & Institute for Health Informatics Director, Center for Nursing Informatics Location - WDH 6-155 P - 612-625-4470, Fax - 612-625-7091 email - westr...@umn.edu Mail - WDH 5-140, 308 Harvard St SE, Minneapolis, MN 55455 On Thu, Sep 11, 2014 at 3:39 PM, Apathy,Nate <nate.apa...@cerner.com> wrote: > Hi Russ, > > > > Dan mentioned to me earlier that this thread was intended for these > discussions, so I copied over our thread from the “notes” chain here for > easier retrieval in the archive. > > > > So far, CMH is implementing Discovere and has been using PowerTrials to > track an adverse-event study for the past couple of years. Discovere is > slated to be fully live by the end of the year, at which point they will > most likely be adding several studies (with a focus on >1y longitudinal > studies). The biggest EHR integration point for Discovere is that there is > an Integrated Data Capture (IDC) function that allows study designers to > map data elements in Cerner to data elements in Discovere for automatic > population of values that are recorded in the Cerner chart, to reduce > duplication and manual data entry. > > > > I think as we flesh these functionalities out further, we'll definitely > find some common points of functionality to leverage for PCORI! > > > > Thanks, > > > > Nate Apathy > > Program Manager, Cerner Research > > > > > > -----Original Message----- > From: Russ Waitman [mailto:rwait...@kumc.edu] > Sent: Thursday, September 11, 2014 9:59 AM > To: Apathy,Nate; Hickman, Hubert B; gpc-dev@listserv.kumc.edu > Subject: RE: GPC Dev notes for 9/9/2014 > > > > Hi Nate, > > Very helpful. > > > > What portions of this are used at CMH today or over the next year or two? > > > > Really look forward to working with you on how much of this Cerner > capability and corresponding Epic capability we can understand how to use > across our network for our PCORI goals, > > > > Russ > > > > -----Original Message----- > > From: gpc-dev-boun...@listserv.kumc.edu [ > mailto:gpc-dev-boun...@listserv.kumc.edu > <gpc-dev-boun...@listserv.kumc.edu>] On Behalf Of Apathy,Nate > > Sent: Thursday, September 11, 2014 8:54 AM > > To: Hickman, Hubert B; gpc-dev@listserv.kumc.edu > > Subject: RE: GPC Dev notes for 9/9/2014 > > > > Hi all, > > > > In reviewing the notes I realized that I never responded to the first > question for Cerner around integrating research into the clinical workflow. > From a Cerner perspective, we have a few solutions that do this, including > PowerTrials, Discovere, and our new OnCore interface that works with > PowerTrials. PowerTrials is a solution for entering protocols and > recruiting patients for a study, and includes an indicator in the banner > bar of each patient's chart who is on a trial, to alert all clinicians that > encounter that individual's chart. PT allows researchers to manage accrual, > recruit patients for studies, and includes a "Clinical Research" tab in the > primary chart that is dedicated to the available clinical trials at the > institution as well as gives providers the ability to check what trials a > patient might be eligible for. Eligibility screenings are built into the > Cerner Millennium system via Discern Rules that can be designed to > logically evaluate the inclusion/exclusion criteria for > > a study within a patient's chart, or across the entire patient > population. > > > > The newest development with PowerTrials, since it is not a full CTMS > within Millennium, is our OnCore interface, which we have established with > our alpha client and are now prepared to implement more broadly. We've been > working closely with Forte to establish that relationship, and one of our > folks, Ryan Moog, is actually at Forte today discussing the next steps for > improving that interface and making the implementation more repeatable > across clients. > > > > Let me know if I need to update the notes and re-send the pdf. > > > > Thanks, > > > > *Nate Apathy* > > Program Manager, Cerner Research > > > > *From:* gpc-dev-boun...@listserv.kumc.edu [mailto: > gpc-dev-boun...@listserv.kumc.edu] *On Behalf Of *Dan Connolly > *Sent:* Monday, September 08, 2014 5:49 PM > *To:* gpc-dev@listserv.kumc.edu > *Cc:* John Steinmetz > *Subject:* Embed research within healthcare systems > > > > In a KUMC GPC planning meeting today, we realized we'd like to identify > leading sites for embedding research withing healthcare systems. > > Who has a well-trodden path to getting changes deployed in your EMR and > clinical workflow? Care to give an example or two? What was the nature of > the change, and about how long did it take to plan and execute? > > The deadlines are a ways out, but my (very limited) experience suggests > that getting changed deployed in a production EMR should be planned well > over 6 months in advance. > > Embed research within healthcare systems > > Jun-15 > > 5.2 > > Randomize patients and/or sites for participation in clinical trials > > Lead sites: Mar-15 > All sites: Aug-15 > > 5.4 > > > > -- > Dan > > CONFIDENTIALITY NOTICE This message and any included attachments are > from Cerner Corporation and are intended only for the addressee. The > information contained in this message is confidential and may constitute > inside or non-public information under international, federal, or state > securities laws. Unauthorized forwarding, printing, copying, distribution, > or use of such information is strictly prohibited and may be unlawful. If > you are not the addressee, please promptly delete this message and notify > the sender of the delivery error by e-mail or you may call Cerner's > corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. > > _______________________________________________ > Gpc-dev mailing list > Gpc-dev@listserv.kumc.edu > http://listserv.kumc.edu/mailman/listinfo/gpc-dev > >
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
