| Literature DB >> 26306263 |
Christopher L Crowe1, Cui Tao2.
Abstract
The amount of time and money required to screen patients for clinical trial and guideline eligibility presents the need for an automated screening process to streamline clinical trial enrollment and guideline implementation. This paper introduces an ontology-based approach for defining a set of patterns that can be used to represent various types of time-relevant eligibility criteria that may appear in clinical protocols. With a focus only on temporal requirements, we examined the criteria of 600 protocols and extracted a set of 37 representative time-relevant eligibility criteria. 16 patterns were designed to represent these criteria. Using a test set of an additional 100 protocols, it was found that these 16 patterns could sufficiently represent 98.5% of the time-relevant criteria. After the time-relevant criteria are modeled by these patterns, it will allow the potential to (1) use natural language processing algorithms to automatically extract temporal constraints from criteria; and (2) develop computer rules and queries to automate the processing of the criteria.Entities:
Year: 2015 PMID: 26306263 PMCID: PMC4525239
Source DB: PubMed Journal: AMIA Jt Summits Transl Sci Proc
Temporal patterns and example criteria from the representative criteria. Many criteria are composed of multiple patterns, the specific segment that exemplifies the pattern is italicized.
| No | |
| No | |
| Patient must be a cancer survivor (defined as | |
| No | |
| No ureteral obstruction before start of trial | |
| Veterans who report | |
| Co-enrollment in therapeutic protocol allowed if begun at least 30 days following the week 20 immunization ( | |
| Test positive on 2 out of 3 | |
| Patients may not have received any cancer therapies | |
| No receipt of more | |
| No | |
| Those not performing moderate levels of activity for | |
| No concurrent sodium fluoride at daily doses | |
| Stable weight - variation of less than 5 kg |
Sample OWL DL and SWRL implementations of select patterns.
| Before: X(?e1), Patient(?p1), hasEvent(?p1, ?e1), hasNormalizedTime(?e1, ?t1), lessThan(?t1, Y) → ValidInstant(?e1) | |
| Y(?i1), hasStartTime(?i1, ?t1) → ValidStart(?t1) | |
| ValidPatient = (hasEvent some ValidInstant) or (not hasEvent some ValidInstant and hasEvent some ValidException) | |
| ValidInstant = X and some overlap some Y |