|
| 1 | +@MISC{Van-Tuyl2023-vp, |
| 2 | + title = "Hiring, managing, and retaining data scientists and Research |
| 3 | + Software Engineers in academia: A career guidebook from {ADSA} |
| 4 | + and {US}-{RSE}", |
| 5 | + author = "Van Tuyl, Steve (ed )", |
| 6 | + doi = {https://doi.org/10.5281/zenodo.8329337}, |
| 7 | + url = {https://zenodo.org/records/8329337}, |
| 8 | + abstract = "The importance of data, software, and computation has long been |
| 9 | + recognized in academia and is reflected in the recent rise of job |
| 10 | + opportunities for data scientists and research software |
| 11 | + engineers. Big data, for example, created a wave of novel job |
| 12 | + descriptions before the term Data Scientist (DS) was widely used. |
| 13 | + And even though software has become a major driver for research |
| 14 | + (Nangia and Katz, 2017), Research Software Engineer (RSE) as a |
| 15 | + formal role has lagged behind in terms of job openings, |
| 16 | + recognition, and prominence within the community. Despite their |
| 17 | + importance in the academic research ecosystem, the value of DS |
| 18 | + and RSE roles is not yet widely understood or appreciated in the |
| 19 | + academic community, and research data, software, and workflows |
| 20 | + are, in many domains, still regarded as by-products of research. |
| 21 | + Data Scientists and Research Software Engineers (DS/RSEs) face |
| 22 | + similar challenges when it comes to career paths in academia - |
| 23 | + both are non-traditional academic professions with few incentives |
| 24 | + and a lack of clear career trajectories. This guidebook presents |
| 25 | + the challenges and suggestions for solutions to improve the |
| 26 | + situation and to reach a wide community of stakeholders needed to |
| 27 | + advance career paths for DS/RSEs.", |
| 28 | + year = 2023, |
| 29 | + keywords = "data science; research software engineering; career guidebook" |
| 30 | +} |
| 31 | + |
| 32 | + |
| 33 | +@ARTICLE{Adler-Milstein2017-id, |
| 34 | + title = "Information blocking: Is it occurring and what policy strategies |
| 35 | + can address it?", |
| 36 | + author = "Adler-Milstein, Julia and Pfeifer, Eric", |
| 37 | + journal = "Milbank Q.", |
| 38 | + publisher = "John Wiley \& Sons, Ltd", |
| 39 | + volume = 95, |
| 40 | + number = 1, |
| 41 | + pages = "117--135", |
| 42 | + abstract = "Policy Points: Congress has expressed concern about electronic |
| 43 | + health record (EHR) vendors and health care providers knowingly |
| 44 | + interfering with the electronic exchange of patient health |
| 45 | + informatio...", |
| 46 | + month = mar, |
| 47 | + year = 2017, |
| 48 | + keywords = "electronic health records; health policy; incentives; |
| 49 | + interoperability", |
| 50 | + language = "en" |
| 51 | +} |
| 52 | + |
| 53 | +@ARTICLE{Barker2024-ox, |
| 54 | + title = "A national survey of digital health company experiences with |
| 55 | + electronic health record application programming interfaces", |
| 56 | + author = "Barker, Wesley and Maisel, Natalya and Strawley, Catherine E and |
| 57 | + Israelit, Grace K and Adler-Milstein, Julia and Rosner, Benjamin", |
| 58 | + journal = "J. Am. Med. Inform. Assoc.", |
| 59 | + publisher = "Oxford Academic", |
| 60 | + volume = 31, |
| 61 | + number = 4, |
| 62 | + pages = "866--874", |
| 63 | + abstract = "OBJECTIVES: This study sought to capture current digital health |
| 64 | + company experiences integrating with electronic health records |
| 65 | + (EHRs), given new federally regulated standards-based application |
| 66 | + programming interface (API) policies. MATERIALS AND METHODS: We |
| 67 | + developed and fielded a survey among companies that develop |
| 68 | + solutions enabling human interaction with an EHR API. The survey |
| 69 | + was developed by the University of California San Francisco in |
| 70 | + collaboration with the Office of the National Coordinator for |
| 71 | + Health Information Technology, the California Health Care |
| 72 | + Foundation, and ScaleHealth. The instrument contained questions |
| 73 | + pertaining to experiences with API integrations, barriers faced |
| 74 | + during API integrations, and API-relevant policy efforts. |
| 75 | + RESULTS: About 73\% of companies reported current or previous use |
| 76 | + of a standards-based EHR API in production. About 57\% of |
| 77 | + respondents indicated using both standards-based and proprietary |
| 78 | + APIs to integrate with an EHR, and 24\% worked about equally with |
| 79 | + both APIs. Most companies reported use of the Fast Healthcare |
| 80 | + Interoperability Resources standard. Companies reported that |
| 81 | + standards-based APIs required on average less burden than |
| 82 | + proprietary APIs to establish and maintain. However, companies |
| 83 | + face barriers to adopting standards-based APIs, including high |
| 84 | + fees, lack of realistic clinical testing data, and lack of data |
| 85 | + elements of interest or value. DISCUSSION: The industry is moving |
| 86 | + toward the use of standardized APIs to streamline data exchange, |
| 87 | + with a majority of digital health companies using standards-based |
| 88 | + APIs to integrate with EHRs. However, barriers persist. |
| 89 | + CONCLUSION: A large portion of digital health companies use |
| 90 | + standards-based APIs to interoperate with EHRs. Continuing to |
| 91 | + improve the resources for digital health companies to find, test, |
| 92 | + connect, and use these APIs ``without special effort'' will be |
| 93 | + crucial to ensure future technology robustness and durability.", |
| 94 | + month = apr, |
| 95 | + year = 2024, |
| 96 | + keywords = "application programming interface; digital health; electronic |
| 97 | + health record; industry", |
| 98 | + language = "en" |
| 99 | +} |
| 100 | + |
| 101 | +@ARTICLE{Gillon2024-vu, |
| 102 | + title = "{ODIN}: Open Data In Neurophysiology: Advancements, Solutions |
| 103 | + \& Challenges", |
| 104 | + author = "Gillon, Colleen J and Baker, Cody and Ly, Ryan and Balzani, |
| 105 | + Edoardo and Brunton, Bingni W and Schottdorf, Manuel and |
| 106 | + Ghosh, Satrajit and Dehghani, Nima", |
| 107 | + journal = "arXiv [q-bio.NC]", |
| 108 | + abstract = "Across the life sciences, an ongoing effort over the last 50 |
| 109 | + years has made data and methods more reproducible and |
| 110 | + transparent. This openness has led to transformative insights |
| 111 | + and vastly accelerated scientific progress. For example, |
| 112 | + structural biology and genomics have undertaken systematic |
| 113 | + collection and publication of protein sequences and |
| 114 | + structures over the past half-century, and these data have |
| 115 | + led to scientific breakthroughs that were unthinkable when |
| 116 | + data collection first began. We believe that neuroscience is |
| 117 | + poised to follow the same path, and that principles of open |
| 118 | + data and open science will transform our understanding of the |
| 119 | + nervous system in ways that are impossible to predict at the |
| 120 | + moment. To this end, new social structures along with active |
| 121 | + and open scientific communities are essential to facilitate |
| 122 | + and expand the still limited adoption of open science |
| 123 | + practices in our field. Unified by shared values of openness, |
| 124 | + we set out to organize a symposium for Open Data in |
| 125 | + Neuroscience (ODIN) to strengthen our community and |
| 126 | + facilitate transformative neuroscience research at large. In |
| 127 | + this report, we share what we learned during this first ODIN |
| 128 | + event. We also lay out plans for how to grow this movement, |
| 129 | + document emerging conversations, and propose a path toward a |
| 130 | + better and more transparent science of tomorrow.", |
| 131 | + month = jul, |
| 132 | + year = 2024, |
| 133 | + archivePrefix = "arXiv", |
| 134 | + primaryClass = "q-bio.NC" |
| 135 | +} |
| 136 | + |
| 137 | +@INCOLLECTION{Hermes2023-aw, |
| 138 | + title = "How can intracranial {EEG} data be published in a standardized |
| 139 | + format?", |
| 140 | + author = "Hermes, Dora and Cimbalnek, Jan", |
| 141 | + booktitle = "Studies in Neuroscience, Psychology and Behavioral Economics", |
| 142 | + publisher = "Springer International Publishing", |
| 143 | + address = "Cham", |
| 144 | + pages = "595--604", |
| 145 | + abstract = "Sharing data or code with publications is not something new and |
| 146 | + licenses for public sharing have existed since the late 20s |
| 147 | + century. More recent worldwide efforts have led to an increase in |
| 148 | + the amount of data shared: funding agencies require that data are |
| 149 | + shared, journals request that data are made available, and some |
| 150 | + journals publish papers describing data resources. For |
| 151 | + intracranial EEG (iEEG) data, considering how and when to share |
| 152 | + data does not happen only at the stage of publication. Human |
| 153 | + subjects’ rights demand that data sharing is something that |
| 154 | + should be considered when writing an ethical protocol and |
| 155 | + designing a study before data are collected. At that moment, it |
| 156 | + should already be considered what levels of data will be |
| 157 | + collected and potentially shared. This includes levels of data |
| 158 | + directly from the amplifier, reformatted or processed data, |
| 159 | + clinical information and imaging data. In this chapter we will |
| 160 | + describe considerations and scholarship behind sharing iEEG data, |
| 161 | + to make it easier for the iEEG community to share data for |
| 162 | + reproducibility, teaching, advancing computational efforts, |
| 163 | + integrating iEEG data with other modalities and allow others to |
| 164 | + build on previous work.", |
| 165 | + year = 2023, |
| 166 | + language = "en" |
| 167 | +} |
| 168 | + |
| 169 | + |
1 | 170 | @ARTICLE{Hanisch2015-cu, |
2 | 171 | title = "The Virtual Astronomical Observatory: Re-engineering access to |
3 | 172 | astronomical data", |
|
0 commit comments