• J. Clin. Oncol. · Sep 2017

    Identifying Health Information Technology Needs of Oncologists to Facilitate the Adoption of Genomic Medicine: Recommendations From the 2016 American Society of Clinical Oncology Omics and Precision Oncology Workshop.

    • Kevin S Hughes, Edward P Ambinder, Gregory P Hess, Peter Paul Yu, Elmer V Bernstam, Mark J Routbort, Jean Rene Clemenceau, John T Hamm, Phillip G Febbo, Susan M Domchek, James L Chen, Jeremy L Warner, and OPO Workshop Members.
    • Kevin S. Hughes, Massachusetts General Hospital, Harvard Medical School, Boston, MA; Edward P. Ambinder, Icahn School of Medicine at Mount Sinai; Peter Paul Yu, Memorial Sloan Kettering Cancer Center, New York, NY; Gregory P. Hess, Symphony Health, Conshohocken; Gregory P. Hess and Susan M. Domchek, University of Pennsylvania, Philadelphia, PA; Peter Paul Yu, Hartford HealthCare Cancer Institute, Hartford, CT; Elmer V. Bernstam, The University of Texas Health Sciences Center at Houston; Mark J. Routbort, MD Anderson Cancer Center, Houston, TX; Jean Rene Clemenceau, Hospital Angeles Pedregal, Mexico City, Mexico; John T. Hamm, Norton Healthcare, Louisville, KY; Phillip G. Febbo, Genomic Health, Redwood City, CA; James L. Chen, Ohio State University, Columbus, OH; and Jeremy L. Warner, Vanderbilt University, Vanderbilt University Medical Center, Nashville, TN.
    • J. Clin. Oncol. 2017 Sep 20; 35 (27): 3153-3159.

    AbstractAt the ASCO Data Standards and Interoperability Summit held in May 2016, it was unanimously decided that four areas of current oncology clinical practice have serious, unmet health information technology needs. The following areas of need were identified: 1) omics and precision oncology, 2) advancing interoperability, 3) patient engagement, and 4) value-based oncology. To begin to address these issues, ASCO convened two complementary workshops: the Omics and Precision Oncology Workshop in October 2016 and the Advancing Interoperability Workshop in December 2016. A common goal was to address the complexity, enormity, and rapidly changing nature of genomic information, which existing electronic health records are ill equipped to manage. The subject matter experts invited to the Omics and Precision Oncology Workgroup were tasked with the responsibility of determining a specific, limited need that could be addressed by a software application (app) in the short-term future, using currently available genomic knowledge bases. Hence, the scope of this workshop was to determine the basic functionality of one app that could serve as a test case for app development. The goal of the second workshop, described separately, was to identify the specifications for such an app. This approach was chosen both to facilitate the development of a useful app and to help ASCO and oncologists better understand the mechanics, difficulties, and gaps in genomic clinical decision support tool development. In this article, we discuss the key challenges and recommendations identified by the workshop participants. Our hope is to narrow the gap between the practicing oncologist and ongoing national efforts to provide precision oncology and value-based care to cancer patients.

      Pubmed     Full text   Copy Citation     Plaintext  

      Add institutional full text...

    Notes

     
    Knowledge, pearl, summary or comment to share?
    300 characters remaining
    help        
    You can also include formatting, links, images and footnotes in your notes
    • Simple formatting can be added to notes, such as *italics*, _underline_ or **bold**.
    • Superscript can be denoted by <sup>text</sup> and subscript <sub>text</sub>.
    • Numbered or bulleted lists can be created using either numbered lines 1. 2. 3., hyphens - or asterisks *.
    • Links can be included with: [my link to pubmed](http://pubmed.com)
    • Images can be included with: ![alt text](https://bestmedicaljournal.com/study_graph.jpg "Image Title Text")
    • For footnotes use [^1](This is a footnote.) inline.
    • Or use an inline reference [^1] to refer to a longer footnote elseweher in the document [^1]: This is a long footnote..

    hide…