Difference between revisions of "May 20"
Jump to navigation
Jump to search
(One intermediate revision by one other user not shown) | |||
Line 6: | Line 6: | ||
* Ana Estelrich (GIP-DMP) - Planning Co-Chair | * Ana Estelrich (GIP-DMP) - Planning Co-Chair | ||
* Joann Larson (Kaiser) | * Joann Larson (Kaiser) | ||
− | * Dan Levy | + | * Dan Levy (Outcome Science) |
* Judy Logan (HL7, OHSU) | * Judy Logan (HL7, OHSU) | ||
* Joan McMillen (RSNA) | * Joan McMillen (RSNA) | ||
* Harry Solomon (GE) | * Harry Solomon (GE) | ||
− | * Gary Walker | + | * Gary Walker (Quintiles) |
* Daemon Whittenberg (Greenway Medical Systems) | * Daemon Whittenberg (Greenway Medical Systems) | ||
Line 44: | Line 44: | ||
## There was a breakout session that was dedicated to creating the CCD to ODM crosswalk. This will be done in the profile by providing a xslt that can be applied to the CCD will create ODM with CDASH mappings. | ## There was a breakout session that was dedicated to creating the CCD to ODM crosswalk. This will be done in the profile by providing a xslt that can be applied to the CCD will create ODM with CDASH mappings. | ||
## There were questions surrounding attaining validation rules for this CDASH compliant ODM. Landen is working on attaining this. | ## There were questions surrounding attaining validation rules for this CDASH compliant ODM. Landen is working on attaining this. | ||
+ | |||
+ | [[Category:Minutes]] |
Latest revision as of 17:13, 21 May 2008
May 20 QRPH Face-to-Face Meeting Minutes
Attendees:
- Floyd Eisenberg (Siemens) Co-Chair
- Jason Colquitt (Greenway Medical Systems) Co-Chair
- Landen Bain (CDISC)
- Ana Estelrich (GIP-DMP) - Planning Co-Chair
- Joann Larson (Kaiser)
- Dan Levy (Outcome Science)
- Judy Logan (HL7, OHSU)
- Joan McMillen (RSNA)
- Harry Solomon (GE)
- Gary Walker (Quintiles)
- Daemon Whittenberg (Greenway Medical Systems)
- Measure Definitions with Value Sets Performance_Measurement_Data_Element_Structured_for_EHR_Extraction
- Overview of knowledge to guideline to clinical decision support to measure model Diagram courtesy Sheila Teasdale, AMA
- Collaborative model may not be sufficient for the expression of quality measures. It does not manage continuous variables (mean, median). Counts for population or denominator are managed, but not the continuous variable.
- Context must be identified to disambiguate the source:
- The section of the CCD or summary to represent the information will attribute different meaning. E.g., Disease may be negated in present history, represent risk in the family history and represent past occurrence in the past medical history.
- CCD doesn’t manage procedure reporting. CDA constrained may help but there is no clear gastroenterology procedure constraint on CDA.
- Element to identify “withdrawal” time for colonoscopy is not clear. There is narrative that the “mean withdrawal time” is required for reporting. The time (in narrative) is from the time at which the cecum is reached to the time of withdrawal (expected > 6 minutes). How such times are expected to be documented is not clearly specified in the measure.
- The measure is only valid for “normal” results for patients with intact colon.
- What is “normal” – no polypectomies, no biopsy are likely requirements – Electronic definition will require assumptions
- What is “intact colon” – no prior resections, etc. – Electronic definition will require assumptions
- White paper will include recommendations for enhancement of such measures:
- Review of measures for detailed specification to manage issues identified
- Request for new SNOMED codes (perhaps)
- Request from appropriate GI expert societies for new structured document or other standard procedure report for Gastroenterology procedures and/or specifically Colonoscopy. Such requests could be made to HL7, DICOM, IHE appropriate domain.
- COL8 Revised - Judy Logan
- Value set Issues:
- Registry – Source of creating value sets. The source will send value sets to a repository so that all metadata, oids, identifiers, versions are available for queries to find the appropriate value set. For Joint Commission measures that update every six months, there is a need to identify earlier versions of value sets for analysis of performance during previous time frames.
- Effective Time – Important to know a range when a value set is initially valid (effective) and when it is no longer valid (expired) and needs to be replaced with respect to versioning. Example with Joint Commission measures there is an effective date for measure modifications (hence value sets) and for expiration and updates (versions) to measures and value sets.
- Language – A value set in a country with two languages (e.g., Canada) requires representation. Language is a preferred string. The value set is represented by the concepts. There may be different preferred strings within the value set, each string representing a different language.
- Obsolete Terms – The value set may have members that have a status of ‘deprecated’ or ‘obsolete’. This issue could be managed with versioning. For example, a medication is no longer valid (removed from the market), or a laboratory test is no longer available.
- Versioning -
- Validation / Security of Value Sets – Potential for incorrect measurements
- Creation of a Value Set
- Mapping to local terms is not in scope for value sets specifically but an implementation issue for incorporation of quality measures within EMR Systems.
- A hierarchically modeled value set would allow use of different levels depending on the implementation site. Relationships to underlying vocabularies remain within those vocabularies.
- Review of value set definitions for Joint Commission Measures AMI3, HF3, OP3 Excel Spreadsheet
- Clinical Research - Working session for mapping CDASH and CCD
- There was discussion around creating a new constraint on CCD specifically for this content profile this will leverage existing PCC templates and allow us to identify the exact sections required for CDASH. These constraints also ensure a consistent structure that should help with mapping to CDASH that is not present in just a compliant CCD document.
- There was discussion around what and how much information should come over from the CCD. The decision was made to send over at minimum display text and that if more info is needed then the Form Manager has the full CCD to refer to, and can supplement the ODM with this extra data where appropriate.
- There was a breakout session that was dedicated to creating the CCD to ODM crosswalk. This will be done in the profile by providing a xslt that can be applied to the CCD will create ODM with CDASH mappings.
- There were questions surrounding attaining validation rules for this CDASH compliant ODM. Landen is working on attaining this.