Control/Query Working Group Meeting Agenda
September27 – October 1, 2004
Atlanta, Georgia
General Editor:
Quarter 3, Monday, September 27, 2004
Topic: Meeting Overview, Co-chair Election; v3 Ballot Overview, v2 Ballot Overview, v3 Proposals
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda approval – this session
3 / San Antonio Minutes Review / 5 ( 1- 3)
4 / Agenda approval – summary for the week / 5
5 / Announcements / 5
6 / Co-chair election / Dependent on the arrival of elections officer / 5
7 / Mission Statement Review
8 / Decision Making Practices Highlights / 5 (7 -8)
9 / Data Types Issues / 45
10 / Status of v3 Infrastructure Management, R1 / 5
11 / Report on v2 and v3 ballot status / 5
11 / V3 proposals - Overview? / 5
12 / Decision on New Application Domain / 5
13 / Adjournment
Data Types issues
# / Description / History20040921: We should recruit another editor for the v3 Data Types Standard. / 20040921: Email from G. Shadow: We should recruit another editor, the person needs to be able to use CVS and to edit the XML sources of the specification directly.
20040921: Review action items from previous ballot reconciliations. / 20040921: Email from G. Shadow: review of action items from previous ballot reconciliations. Some may imply further changes.
20040921: SLITS<T>:Add a way to represent NULL values in the sequence. / 20040921: Email from G. Shadow: SLITS<T>: add a way to represent NULL values in the sequence.
We wanted to add something about using the symbol “\NA” in the SLIST<T> datatype to mean “no value”. This may actually be just an XML ITS question.
20040921: PIVL<TS> add a property called frequency. / 20040921: Email from G. Shadow: PIVL<TS> add a property called frequency. This property will co-exist with period and will have type RTO<INT, PQ of time>
It will be made clear in the narrative that frequency is semantically equivalent to period, but is available as an alternative representation. In the XML ITS, only one of the components frequency and period can be valued in any instance.
20040921: EIVL<TS>: Deprecate many of the current event codes that are of the form Ax, Px, Ix (ante-x, post-x, inter-x), such as ACV, PCV, ICV. / 20040921: Email from G. Shadow: EIVL<TS>: Deprecate many of the current event codes that are of the form Ax, Px, Ix (ante-x, post-x, inter-x), such as ACV, PCV, ICV. Instead put in codes for simply C, CM, CD, CV, etc. to indicate the event. Then the offset interval would be interpreted as follows: negative offsets are measured from the start of the event (e.g., 30 min before breakfast) and positive offsets are measured from the end of the event (e.g., 2 hours after meals.) The problem with the present definition is that the offset direction (whether it is before or after) is indicated by the sign AS WELLAS the event code.
20040921: EIVL<TS> add event codes / 20040921: Email from G. Shadow: EIVL<TS> add the following event codes (with the offset semantics as specified in previous change)
COIT Sexual intercourse
DIAP Diaper change
DEFEC Defecation
20040921: ANY: add originalText property to (most) any data types. / 20040921: Email from G. Shadow: ANY: add originalText property to (most) any data types, so that they would be just inherited to CD or PQR, and available for all data types. The XML ITS does not need to allow for originalText for each and everything, but most RIM attributes end up having a place to put original text.
20040921: GTS literal form: add another specialization of SXCM<TS> in the XML ITS for GTS with literal forms. / 20040921: Email from G. Shadow: GTS literal form: add another specialization of SXCM<TS> in the XML ITS for GTS with literal forms. It would actually look like a CE:
<effectiveTime code="JHUSMEM"/>
<effectiveTime code="JHUSLBR" operator="P"/>
Which would be the all the seasons between memorial day and labor day. CodeSystem would be an optional attribute to override the default standard GTS codes for local codes.
20040921: PPD<T>: Revamp PPD to address two interests in the PPD data type extension. / 20040921: Email from G. Shadow: PPD<T>: we have two interests in the PPD data type extension. One group of people (Paul Schluter, GE, from LABPOCT SIG and IEEE/MIB group) wants more distribution types and more parameters.
Another group, represented by many, many casual users, need a simple confidence-interval like form. Those are people who now prefer to use IVL<T> rather than PPD because PPD seems alien to them.
Proposal is to revamp PPD (which had been left on status informative for the ballot) and accomplish both of these above goals. Review and extend the distributions and parameterization model, and at the same time add a confidence interval form and potentially a percentile form.
The goal is to make PPD/confidence interval and IVL compatible types with the same XML rendition. That way we can gently stir people to using PPD for ranges with "pick one" semantics and away from IVL which has "all of those" semantics.
Quarter 4, Monday, September 27, 2004
Topic: Joint CQ/Conformance session; v2.6 ballot resolution
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda Approval
3 / Announcements
4 / Evaluate need for Joint Session in Orlando
5 / Action Items
6 / Ch 2B Ballot Response - Editorial Items / Block vote
7 / Ch 2B Ballot Response -Negatives and Related Items
8 / Ch 2B Ballot Response - Affirmative Comments
9 / Adjournment
Action Items
# / Description / Who / History/Update / Status20040503: Establish chapter 2B / J Larson / Done
Quarter 1, Tuesday, September 28, 2004
Topic: Joint Meeting with PM, PA and CQ. Registry patterns Project and miscellaneous items.
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda Approval
3 / Announcements
4 / Evaluate the Need for a Joint Meeting in Orlando
5 / Action Items
6 / Registry Patterns Project
7 / Prop 912 (MFMI) New Master File D-MIM
8 / Adjournment
#
/Deliverables and Action Items
/Assignee
/Due
/Status
0 / Project Organization and MgmtProject Charter / Closed
Appoint Project Leader
Appoint Scribe
Notify co-chairs of participating committees about current project plans (june 2/04) / Scott R.
1. / Agreement of Terms and Definitions
1.1 / Draft terms and definitions using existing white papers, etc. / Bob G / 6/2/04
1.2
2. / Agreement on Starter List of Registries
2.1 / Request samples of Registry storyboards and Use Cases / Jean S / 5/26/04
2.2 / Assemble Storyboards and Use Cases into one document / June R / 6/9/04
3. / Agreement on a business model and validate for Registry Types
3.1 / Identify the Patient Administration content that may be affected by the project recommendations / Gregg S
3.2 / Collate use case / business model submissions / June R.
4. / Is there a Pattern, Deviations from the Standard Model, Changes to Model Required
5. / Evaluation of MFMI Infrastructure and Dynamic model that exists
6. / Recommendations for HL7 Publishing
7. / Resolve question as to whether Registry Pattern to be balloted as Normative
8. / Organize Project meeting at Atlanta WGM, (Sept 26-30)
Enquire about meeting space and time for Registry Patterns Project meeting(s) at Atlanta WGM. / Scott R.
Quarter 2, Tuesday, September 28, 2004
Topic: Shared Messages Ballot Reconciliation and Proposals
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda Approval
3 / Announcements
4 / Action Items
5 / Shared Messages Ballot Reconciliation
6 / 904 / Prop 904 Extend R-MIM, comparison with the IHE XDS profile
7 / 908 / Prop 909 Add Application Acks to Act Reference topic
8 / Adjournment
Action Items
# / Description / Who / History/Update / Status<include date>
Quarter 3, Tuesday, September 28, 2004
Topic: v2.6 Ballot Reconciliation
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda Approval
3 / Announcements
4 / Action Items
5 / Ballot Reconciliation - Editorial Items for 2, 2A, 5, 8 and 14 [if not addressed previously] / Block vote
6 / Ch 5 Ballot Reconciliation - Negative and Related Items
7 / Ch 8 Ballot Reconciliation - Negative and Related Items
8 / Ch 14 Ballot Reconciliation - All Items
9 / Ch 5 Ballot Reconciliation - Other Items
10 / Ch 8 Ballot Reconciliation - Other Items
11 / Adjournment
Action Items
# / Description / Who / History/Update / Status1Q4-01 / 20030908: Refer table for Protection Code to Vocab for consideration / Joann Larson / 20040105: CQ Telcon: Joann L reported that this has not yet been done
20040505: Joint CQ/Vocab: Vocab feels that this table is not a Vocab issue. General guidelines for determining what table issues to bring to Vocab were. They are interested in clarifying rules as necessary regarding the addition of new values. They are also interested in pre and post coordination of table values. / Open
1Q4-04 / 20030908: Check with Vocab chairs to see if they want to look at changes to table 0201 / Roll forward to Vocab meeting
20040505: Joint CQ/Vocab: Changes to both Table 0201 - Telecommunication Use Code and HL7 Table 0202 - Telecommunication Equipment Type were reviewed. These tables meet the new criteria for Vocab review in that they involve pre and/or post coordination. / Open
2Q2-01 / 20030909: Confirm example for Sending Network Address that references IPV4 / Joann Larson / Need review of the example (take up Q4)
20040607: CQ Telcon: Examples were reviewed as part of the final disposition of the proposal. Examples are believed to be correct. / Open
3Q1-01 / 20030910: Model the 7 query types defined in chapter 5 in Messaging Workbench. / Jenni Puyenbroek / 20040105: Larson: According to the minutes, this was completed. Was it assigned and completed on the same day? Is this a copy and paste error? (take up Q4) / Open
5Q1-01 / 20030912: take length discrepancies for certain item numbers to ARB. Our feeling is that it is legitimate to have different lengths. / Joann Larson / Open
5Q2-01 / 20030912: Determine format for metadata tables / Open
Quarter 4, Monday, September 27, 2004
Topic: CQ/Security and Accountability Joint Meeting
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda Approval
3 / Announcements
4 / Evaluate need for Joint Session in Orlando
5 / Action Items
6 / Ch 2 Ballot Response - User Authentication Credential (UAC) / Glen Marshall
7 / Role-Based Access Control status / Dawn Rota
8 / Integrating the Health Care Enterprise (IHE) Report / Glen Marshall
9 / Common Audit Message document:
IETF and IHE actions / Glen Marshall
11 / ISO/TC 215 activity report, proposals for HL7 coordination / Bernd Blobel
12 / Other S&A Activity
13 / Adjournment
Action Items
# / Description / Who / History/Update / Status20040504: update the Kerberos proposal in accordance with the discussion and post it to the group / G Marshall / Done
Quarter 1, Wednesday, September 29, 2004
Topic: Miscellaneous Issues and Transport Specifications
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda Approval
3 / Announcements
4 / Action Items
5 / Transmission wrapper field - resubmission indicator
6 / 901 / Prop 901 Abstract Transport Specification including Integrated State Model for 806 and 901
7 / 803 / Prop 803 Message Routing
8 / RouterState Model
9 / RelayState Model
10 / 908 / Prop 908 (IM?) HL7 Ping [unless addressed elsewhere]
11 / Transport Overview Status / Paul Knapp
12 / WS-Enhancements: Security Profile / Roberto Ruggeri
13 / WS-Enhancements: Reliable messaging / Roberto Ruggeri
14 / WS-Enhancements:Addressing / Roberto Ruggeri
15 / Adjournment
Action Items
# / Description / Who / History/Update / Status<include date>
Quarter 2, Wednesday, September 29, 2004
Topic: v2.6 Ballot Reconciliation
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda Approval / Continuation of 2Q2 agenda if needed
3 / Announcements
4 / Action Items
5 / Shared Messages Ballot Reconciliation - Editorial items [if not done previously] / Block vote
6 / Shared Messages Ballot Reconciliation - Negative Items [if not done previously]
7 / Shared Messages Ballot Reconciliation - Other Items [if not done previously]
8 / 904 / Prop 904 Extend R-MIM, comparison with the IHE XDS profile [if not done previously]
9 / 908 / Prop 909 Add Application Acks to Act Reference topic [if not done previously]
10 / 912 / Prop 912 New MFMI Wrapper / 45
11 / Adjournment
Action Items
# / Description / Who / History/Update / Status<include date>
Quarter 3, Wednesday, September 29, 2004
Topic: Joint CQ/Vocab meeting on v2 and v3 issues
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order at 1230
2 / Agenda Approval
3 / Announcements
4 / Evaluate need for Joint session in Orlando
5 / Use of UCUM in the PQ data type
6 / Action Items
7 / V2 Table 0396 Stewardship
8 / V2 Table Description (Section 2.5.3.6) Stewardship
9 / V2 CNE and CWE Data Types Stewardship
10 / V2 Ballot Reconciliation
11 / V3 DisplayName and DisplayText / Description Identifier
12 / V3 CTS data type usage
13 / V3 Usage problems with CD data type
14 / Adjournment
Action Items
# / Description / Who / History/Update / Status20040505: See section 2.A.89.4. The narrative needs to be updated to reflect decisions made with proposal 335 / Graham
3Q3-03 / 20030430: The coding rationale in the CD data type needs to be put into the rest of the appropriate data types, such as CE, CV and CS. / Grahame Grieve / 20040105: CQ Telcon: Grahame believes this item is not stated correctly. Refer back to joint mtg for clarification
20040505: Added to today’s agenda. / unclear
3Q3-04 / 20030430: The recommendation is to make the changes to the data type abstract specification where examples similar to this would be added. / Grahame Grieve / 20040105: CQ Telcon: Grahame reported that this item is still outstanding - actively in progress over the last several days.
3Q4-09 / 20040505: Stan to send the originalText and displayname changes / Stan
3Q4-10 / 20040505: CTS document and Java SIG use same package name org.hl7.types
3Q4-11 / 20040505: We will raise the use case for the CD changes at harmonization, and publish something in the draft at the next publication cycle
Quarter 4, Wednesday, September 29, 2004
Topic: v3 Transports
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda Approval
3 / Announcements
4 / Action Items
5 / 901 / Prop 901 Abstract Transport Specification including Integrated State Model for 806 and 901 [Unless addressed in 3Q1]
6 / 803 / Prop 803 Message Routing [Unless addressed in 3Q1]
7 / RouterState Model [Unless addressed in 3Q1]
8 / Relay State Model[Unless addressed in 3Q1]
9 / 908 / Prop 908 (IM?) HL7 Ping [unless addressed elsewhere]
10 / Transport Overview Status [Unless addressed in 3Q1] / Paul Knapp
11 / WS-Enhancements: Security Profile [Unless addressed in 3Q1] / Roberto Ruggeri
12 / WS-Enhancements: Reliable messaging [Unless addressed in 3Q1] / Roberto Ruggeri
13 / WS-Enhancements:Addressing [Unless addressed in 3Q1] / Roberto Ruggeri
14 / Adjournment
Action Items
# / Description / Who / History/Update / Status4Q3- / 20040506: Create a normative “requirements for transport specifications” document. / Rene / 20040506: The document will be based on an agreed set of use case, with the goal of creating a common framework Rene will chair the task force and report back next WGM This will require a new transport overview.
4Q3- / 20040506: Add language regarding ReplyTo to the transport intro and MCCI
3Q2-01 / 20040505: Evaluate need to include an end-to-end commit ack in the transport requirements documentation. / Paul Knapp / 20040505: Mark Tucker identified a use case for an end-to-end commit ack. This needs to be discussed by the (future) transport taskforce for possible inclusion in the transport requirements documentation. / Open
02 / 20040809: Transports Intro document to be updated
1 / 20040816: Submit comments and work on nomenclature and return Transport Requirements document to René / Roberto R / 20040823: Roberto will create an update before Thursday 26th and send to rene as well as the Transports list.
2 / 20040816: submit a clarification of the routing section as follows: 1. replace the term Relay with Gateway 2. Address routing maps under the routing section / Paul K
Quarter 1, Thursday, September 30, 2004
Topic: Joint CQ/XML meeting
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda Approval
3 / Announcements
4 / Evaluate Need for Joint Session in Orlando
5 / Action Items
6 / XML Implementation
Guide Status
7 / XML ITS Structures status
8 / XML ITS Data Types status
9 / Adjournment
Action Items
# / Description / Who / History/Update / Status2Q1-01 / 20030114: We need to document difference between abstract specification and XML ITS DataTypes. Andrew H will get list of differences from Paul. / Grahame Grieve / 20040105: CQ Telcon: Grahame reported that this is still in progress
20040506: Still open – slated for release 2 / open
4Q1-01 / Action: Discover if there is further issue with respect to caching of schemas for different versions of interactions. / Roberto/Charlie/Paul Biron / 20040506: To agenda / Open
4Q1-02 / Charlie will Consult with PA (Gregg Seppala) r.e. codes from V2 to see if there are use cases (#80 postal address use) / Charlie / 20040506: Still open / Open
4Q1-03 / Potential Action: if there are use cases (#80 postal address use), then a harmonization proposal will be crafted by GG. / Grahame G / 20040506: Dependent on 4Q1-02 above / Open
4Q1-04 / 20040506: Fix the CR data type / Grahame G / 20040506:CR is marked in the ITS as an extension of CD, both in the schema and the type template. This is in error, as it should be an extension of ANY.
Paul: This is a legacy of the past where CR did extend CD
4Q1-05 / 20040506: complete the definition of codingRationale. / Grahame G / 20040506: CodingRationale was added to the Abstract Data types at the request of the vocabulary committee, but not completed in either the abstract data types, or the ITS documents. The vocabulary domain has been defined and populated by the vocabulary committee. This must be handled as a technical correction, with a choice of completing the definition of codingRationale, or removing it completely.
4Q1-06 / 20040506: Determine if schemas are in or out of the specification / 20040506: The committee was unable to come to consensus over these issues. Discussion was terminated, to be continued on a teleconference that will be announced on the xml and cq email lists
7 / 20040524: Telcon: Create list of editorial changes for XML ITS Data Type / Grahame G / 20040607: CQ Telcon: Grahame G reported that the list of editorial corrections in progress.
8 / 20040524: CQ Telcon: Schema fragments to be removed from ITS document to the Appendix
9 / 20040524: CQ Telcon: Submit XML ITS Data Type document by July 2 to CQ TC and XML SIG for e-mail straw vote closing July 9 establishing the committees' view that the changes made are not substantive.
10 / 20040524: CQ Telcon: Submit changes to XML ITS Data Type document to ARB for binding confirmation if CQ believes they are NOT substantive
11 / 20040524: CQ Telcon: Create list of editorial changes to the XML ITS Structures document / Charlie McCay
Quarter 2, Thursday, September 30, 2004
Topic: v2.6 Ballot Reconciliation
Agenda
# / Key / Description / Presenter / Action Needed / Time1 / Call to Order
2 / Agenda Approval
3 / Announcements
4 / Action Items
5 / Ch 2 Ballot Reconciliation - Negative and Related Items
6 / Ch 2A Ballot Reconciliation - Negative and Related Items
7 / Ch 2 Ballot Reconciliation - Other Items
8 / Ch 2A Ballot Reconciliation - Other Items
9 / Continue 2Q3 agenda as needed
10 / Adjournment
Action Items
# / Description / Who / History/Update / Status<include date>
Quarter 3, Thursday, September 30, 2004