Structured Document TC Meeting Minutes

Structured Document TC Meeting Minutes

December 9, 2010

Name / Organization / E-Mail Address
x / Liora Alschuler / Alschuler Associates, LLC /
Austin Kreisler / Science Applications International Corp /
x / Bonnie McAllister / Iatrics Systems /
x / Diana Behling / Iatric /
x / Bob Dolin / Semantically Yours, LLC /
Rick Geimer / Alschuler Associates, LLC /
Grahame Grieve / kestral
Bonnie McAllister
Clayton Curtis (VA)
Crystal Kallem
David Shields – Duke
Diana Behling
Floyd Eisenberg
Gail Cox
Gay Giannone
Guilherme Del Fiol
Helmet Koenig (Siemens)
Howard Stasberg (WK)
Jan Kwon
Jane McKnight
John Roberts
Juggy Jagannathan
Robert Jenders
Kate Hamilton
Kenny Landry
Kensaku Kawamoto
Li Zhou
Mary Ann Juurlink
Max
Peter Gilbert
Peter Haug
Richard Thoreson
Rita Altamore (WA DOH)
Rob Hausam
Rob McClure
Ron Dionne
Serafina Versaggi
Thomas Pole
Ioana Singureanu
Thomson Kuhn
vhuser

Note: Attendees denoted with “X”.

Agenda

ItemDescription
RoleCall 5 min
Agenda Review
1. Joint meeting w/Decision Support on eMeasure/QDS
2. Updates
3. CBCC Semantic Health Information Performance and Privacy
4. HAI
5. Preview of next week’s R3

1. Joint meeting w/Decision Support on eMeasure/QDS

Using HITEP Quality Data Set to construct criteria for eMeasures; align w/C32 templates, coupling CCD-capable EHR with quality reporting. How can we apply same approach to decision support?

QDS: as DAM? as US Realm eMeasure IG? Discussion today is to consider these alternatives moving to a Project Scope Statement.

Floyd: prototype and test, provide for ballot? DAM vs IG?

Ken Kawamoto: overlap w/Virtual Medical Record; also, how to express concepts? (Gello, Arden...)

Bob: addressing expressivity, would like to bring forward RIM Harmonization proposal that would allow more than a string to express these concepts; another issue to address is “EHR context”, similar to issues raised in context of InfoButton.

Guilherme Del Fiol: do have something for context

Bob: can express derivation express and state the syntax (default is string); can enhance the syntax options to include Gello, SQL, etc.

? : What are the use cases?

Bob: Q measures are awkward without a formal syntax for derivation

Floyd: is this needed?

Ioana: focus on common concepts, no need for special syntax, special language

Bob: four big areas:

• what to do w/QDS?
• how do we describe expressions in eMeasure?
• express context?
• how do view end to end process?

Should we prioritize?

Ken: prioritization is good, should be driven by those doing the work – Bob, SDWG, Dec Supp.

Bob:

#2: extending eMeasure is relatively small, Bob has volunteered to do this. Can draft, review w/Decision Support. Extending measures with expression language: Bob and Floyd will gather examples. Ken suggests framing as pseudo code. Will lead to PSS.

#1: QDS w/possible US Realm IG showing data criteria, population criteria. 3 options:

a) ballot DAM for QDS, through CIC or SDWG or DSWG

b) define how QDS and CCD work together w/in DS service model to support EHR qurery, extract;

c) middle path: US Realm HQMF Implementation Guide; show how QDS is used as building block for eMeasure criteria w/in the US

Li: the method of linking the value sets is also a problem; Keith: Data Types R2 will address this; Discussion on binding of value sets – at QDS/QDE level?

Robert Jenders (just joining): IG direction seems feasible

Bob: suggest we move ahead w/c). Ken endorses, aligns with primary stakeholders. Floyd, addresses immediate needs. Any dissent? None, just a question of writing up the PSS.

Some discussion of timeframe: Keith, May could be too soon. Liora: consider in context of PSS.

Bob: will list both WGs as co-sponsors.

1. Updates
2. OIDs: next week; P2P: next week;
3. Pilot: scope statement pending; Mapping: scope pending

1. CBCC Semantic Health Information Performance and Privacy

Review data segmentation from perspective of privacy and computation. Take example from behavioral health, apply to other domains.

Juggy: why have excluded narrative data?

Ioana: unless enriched, not useful for real time computing, rules processing; will look at in terms of level of maturity. More structured, more useful it is.

Bob: what is the deliverable? functional spec, DAM? Ioana: DAM and enhancement to EHR Functional model. Method: review consent directives and HEDIS and other measures.

Complementary to QRDA and eMeasure, looking at where the information is within the EHR. QDS useful for defining the components of measures. Value sets will differ per domain.

Liora: recommend SDWG support; suggest clarification of Scope to indicate intent, deliverables, relationship to current HL7 quality DSTUs.

Crystal: please clarify sense of “data quality”.

Liora: move to co-sponosor; Ioana: second; no opposed, or abstain.

.

1. HAI

How to describe a subset of a facility, “all units except...”. Several alternatives. Use location and criteria.

.

1. Preview of R3 Topics

Header & authentication.

.

Adjourned 5pm ET

HL7 - SDTC Meeting MinutesPublished:10/21/18