INM Action Items

Open Action Items. Each item may be edited individually. New item numbers in the 2xxx range

Back to Infrastructure and Messaging TC == ITEM: 1 == Opened: 12-Jan-03 We need to document difference between abstract specification and XML ITS DataTypes. Andrew H will get list of differences from Paul Biron.

• 05-Jan-04 , Grahame Grieve , New , XML
  • INM Telcon: Grahame reported that this is still in progress
• 06-May-04 , Grahame Grieve , Open , XML
  • Still open – slated for release 2
• 30-Sep-04 , Grahame Grieve , Open , XML
  • CQ WGM: deferred and slated for R2
• 24-Jan-05 , Grahame Grieve , Open , XML
  • INM WGM Orlando: no change
• 02-May-05 , Grahame Grieve , Open , XML
  • INM WGM Noordwijkerhout: no change
• 05-May-05 , Grahame Grieve , Defered , XML
  • we still think this is a good idea, but no progress yet. May happen as part of R2
• 15-Sep-05 , Paul Biron , Open , XML
  • 20050915 WGM Give to Paul – part of a way to generate requirements for R2
• 28-Nov-05 , Paul Biron , Reviewed , XML
  • 20051128 Paul will try to have content for Phoenix

== ITEM: 15 == Opened: 24-Jan-05 Old Item: 203 For Version 2.7, add language to Chapter 2 to the effect that CQ does not express an opinion at this time on the restarting of set IDs relative to groups or message.

• 24-Jan-05 , Tony Julian , Open , V2
  • INM WGM Orlando: Motion approved 20050506: edit needs to be done in 2.7
• 26-Aug-05 , Tony Julian , Open , V2
  • 20050826: Larson: this item needs a proposal submitted to the v2 database and then it can be closed.
• 28-NOV-05,Tony Julian,Reviewed,V2,20051128 This cannot be done until V2.7 is opened.

== ITEM: 27 == Opened: 26-Jan-05 Old Item: 215 Present Units proposal to Facilitators Roundtable on Jan 27

• 26-Jan-05 , Grahame Grieve , New , vocab
  • INM/Vocab WGM Orlando: Agreed to prepare a proposal for Faciliator’s Roundtable. Within the PQ datatype Unit: change from CS to CV and allow the domain to be set in the model. Could set a domain and call it
• 04-May-05 , Grahame Grieve , Open , vocab
  • Changed from New to Open, assigned Grahame.
• 14-Sep-05 , Grahame Grieve , Open , vocab
  • 20050914: IM WGM San Diego: Close – Stan has developed proposal
• 28-NOV-05 , Grahame Grieve , Open , vocab
  • 20051128: Open pending verification

== ITEM: 32 == Opened: 27-Jan-05 Old Item: 220 CQ WGM: ask the Conformance SIG to work on a dynamic discovery message for supported features by the receiver (profile ids, application roles, interactions, responseModeCodes)

• 27-Jan-05 , INM Chairs , New , conform
  • INM WGM Orlando: Added. Ask the Conformance SIG to work on a dynamic discovery message for supported features by the receiver (profile ids, application roles, interactions, responseModeCodes)
• 02-May-05 , Lisa Carnahan , Reviewed , conform
  • 20050502: Clarified that this is v3, not v2. Len Gallagher has been writing a white paper on the dynamic model which may have some bearing on this item.
• 14-Sep-05 , Lisa Carnahan , Reviewed , Conform
  • 20050914: Conformance says they do not do this; only have conformance for V2.
• 16-Sep-05 , MNM , Open , Conform
  • 20050916: Rene says move to MnM. They are responsable for conformance in v3. The discussion may lead to the conclusion that we don't want to cover this, but that we want to leave this to services such as UDDI.
• 16-Sep-05 , MNM , Reviewed , Conform
  • 20050916: To be reviewed in Phoenix.
• 20060113, Conformance
  • Rene: Met with MnM/Conformance. In principle they see value in this suggestion. Planned to be discussed during the joint meeting of Conformance/INM next WGM.

ITEM: 33

Opened: 28-Jan-05 Old Item: 221

The detectedIssue CMET should be moved to the CMET domain, and not be defined locally in MCAI

• 20050128, INM Chairs, Open
  • INM WGM Orlando: Added. When creating the next version of MCAI, the detectedIssue CMET should be moved to the CMET domain, and not be defined locally in MCAI Pharmacy has a use-case for a message that shows all controlActs(+detectedIssue) related to a single order. This can be implemented today as a shared message. If implemented as a wrapper this would require that the tools support stubs with exit points.
• 20051105, INM Chairs, Open
  • Rene: will remain open until such time where the controlAct domains will be up for a new release.
• 20051128, INM Chairs, Reviewed
  • No Update

ITEM: 34

Opened: 28-Jan-05 Old Item: 222

Need to create a controlAct wrapper for “event replay”.

• 20050128, INM Chairs, New
  • INM WGM Orlando: Added. Need to create a controlAct wrapper for “event replay”. Pharmacy has a use-case for a message that shows all controlActs(+detectedIssue) related to a single order. This can be implemented today as a shared message. If implemented as a wrapper this would require that the tools support stubs with exit points. (transmission wrapper - controlAct - order - 1..n - historic control acts)
• 20051103, INM Chairs, open
  • Rene: will remain open until such a time when the control act domains are up for ballot again. Lloyd McKenzie will have to provide input in this.
• 20051128, INM Chairs, Reviewed
  • No Update

== ITEM: 71 == Opened: 29-Sep-04 Old Item: 318 Draft procedure for agreeing to updates to 396. Will bring draft to CQ.

• 12-Jan-05 , Stan Huff , New , vocab
  • Larson: The procedure should incorporate the decision made at the Atlanta WGM as follows: “All changes to sections for which Vocab is the steward, must be submitted to the v2 change proposal database.”
• 04-May-05 , Stan Huff , Open , vocab
  • INM Noordwijkerhout: Stan will wridte procedure. It will include 1) submit to database ; 2) vocab reviews and makes decision taking in to account such things as redundancy, version and other policy requirements; 3) once approved is immediately valid; 4) notify INM editor Policy needs good definitions but also need to focus on operational factors.
• 01-Jun-05 , Stan Huff , Open , vocab
  • Vocab Telcon: Discussion – Table 396 issue:-HL7 v2.x table 396 is the table of tables. One of the changes in 2.6 was to make content extensible without requiring a re-ballot. Need to document the process of how we put new entries, or update entries to table 396. Current process is to submit a V2.x proposal through the HL7 website.-Proposed solution is that every time a terminology is registered in the OID it would automatically go into Table 396 I V2.x. Vote taken and passed.-The content of tables is only available through the ballot, the document can be updated but there is no place online that you can look it up. Same problem of how to
• 15-Sep-05 , Tony Julian , Reviewed , vocab
  • 20050914: Approved. Tony will check to see if in the substantivity guide.
• 28-Nov-05 , Tony Julian , Reviewed , vocab
  • 20051128 Telcon - Open with Guilt!.

== ITEM: 107 == Opened: 02-May-05 Old Item: 404

Will provide list of terms

• 02-May-05 , Lisa Carnahan , New , Conform
  • INM WGM: Will provide list of terms
• 12-Sep-05 , Lisa Carnahan , Open , Conform
  • 20050912:INM WGM SanDiego. Lisa not present – will review.
• 28-Nov-05 , Lisa Carnahan , Open , Conform
  • 20051128 INM Telcon: will review in Phoenix.

== ITEM: 108 == Opened: 02-May-05 Old Item: 405

Provide definition for realm

• 02-May-05 , Lisa Carnahan , New , Conform
  • INM WGM
• 12-Sep-05 , Lisa Carnahan , Open , Conform
  • 20050912:INM WGM SanDiego. Lisa not present – will review.
• 28-Nov-05 , Lisa Carnahan , Open , Conform
  • 20051128 INM Telcon: will review in Phoenix.

ITEM: 110

Opened: 02-May-05 Old Item: 407

Complete the documentation for Option #2 and resolve the format of the URN (MCCI)

• 02-May-05 , Charlie McCay , New , Attachments and II/IIRef ** Noorwijkerhout
• 28-Nov-05 , Charlie McCay , Open , MCCI
  • 20051128 INM Telcon: Move to MCCI
• 20060110, Charlie McKay, Open
  • 20060110: WGM: Probably URI instead of URN – related to IIRef discussion. No update.
• 20060412, Charlie McKay, Open, Data types
  • 20060412: Charlie McKay: part of datatypes R2 work - will require a proposal.

== ITEM: 132 == Opened: 01-Jul-04 Old Item: 518 Request PIC to create a process to ensure that those that bring forward v2 proposals should include a v3 mapping analysis

• 01-Oct-04 , Doug Pratt , New , Admin
  • Not always possible (some elements are V2 artifacts) but the analysis needs to be done always.
• 05-May-05 , Doug Pratt , Open , Admin
  • 20050506: Doug will ask PIC about status.
• 16-Sep-05 , Joann Larson , Open , Admin
  • 20050916: Joann will take to PIC
• 28-Nov-05, Joann Larson , Open , Admin
  • 20051128 INM Telcon: Joann will take to PIC
• 20060508 WGM San Antonio, open
  • 20060508 WGM: We think this is on the PIC agenda. Rene is attending this Thursday. Noted that Robert Worden is trying to attend all groups having v2/v3 agenda items.

== ITEM: 179 == Opened: 12-Jan-05 Old Item: 946

Explore Single set of rules for sending Attachments with v3 messages and documents

• 12-Jan-05 , INM Chairs , Open , Vocab
  • Added by Larson following receipt of email from Bob Dolin on as follows: “We’ve created two new MIME types for use with structured documents that we’d like to officially register with INM. The first (text/x-hl7-text+xml) is used to constrain Act.text. The second (text/x-hl7-title+xml) is used to constrain Act.title, which was changed from ST to ED datatype at the last harmonization meeting. Each of these types are undergoing ballot - the former is part of CDA and SPL, the latter is part of SPL. Can you let me know how to proceed?.”

Later conversation with Bob revealed these 2 new MIME types were heard and approved in RIM Harmonization. What do we do with them now? Is this a v3 or a v2 issue or both? Should these items be added to v2 t Imported Table 0834 “MIME Types” for use in component 3 “Type of Data” in the RP Reference Pointer data type? If so, it would be an HL7 added value to an external table. Or, should it be added to External Table 0291 “Subtype of Referenced Data” as an HL7 enhancement. It would live there alongside our other HL7 enhancement

• 26-Jan-05 , INM Chairs , Open , Vocab
  • INM/Vocab WGM: Add them to v2.7. Grahame will add to the data types document for release 2.
• 04-May-05 , INM Chairs , Open , Vocab
  • INM/Vocab WGM Noordwijkerhout: Confirmed that these are planned for v2.7 and release 2 of v3 data types.
• 16-Sep-05 , INM Chairs , Open , Vocab
  • 20050916: Need to confirm that these changes are on the change list for 2.7 and for V3 Data Types
• 28-Nov-05 , Paul Biron and Doug Pratt, Open , Vocab
  • 20051128 INM Telcon: Paul will talk to Bob about text/x-hl7-text+xml. Doug will take on for V2.

== ITEM: 961 == Opened: 11-Aug-05 Old Item: 0 Developing a list of basic criteria for shared messages, so that shared messages doesn’t end up being a dumping ground. Perhaps a topic in MCCI R2?

• 11-Aug-05 , Lloyd McKenzie , Open , MCCI
  • INM requests more details. Lloyd will provide them to Tony, and we will discuss the topic in San Diego. Lloyd to start a discussion thread about “undo” on MnM list server. Rene will bring forward notification interactions shared messages. Hope to publish shared messages in January cycle. Lloyd to offer help with shared messages publication database
• 11-Aug-05 , Lloyd McKenzie , Open , MCCI
  • Lloyd added a fifth: sending out a “broadcast” message – such as a user notification that the system is going down in 5 minutes, etc. Lloyd needs to forward this last one to INM.
• 28-Nov-05 , Lloyd McKenzie , Reviewed , Shared Messages
  • 20051128 INM Telcon: no update.
• 20060110, Michael van Campen, Shared Messages
  • 20060110: INM WGM: Michael van Campen will create a list of candidates to be included/excluded. Rene will assist.
  • 20060508 WGM: Open.

== ITEM: 965 == Opened: 13-Sep-05 Old Item: 0 Develop a questionnaire so that groups can submit use case attributes and get the best possible recommendation from Security TC. This will be done through a dialogue. Discussion of transforms needs to take place in this context.

• 13-Sep-05 , Glenn Marshall , New , Security
  • 20050913 WGM NEW.
• 28-Nov-05 , Glenn Marshall , New , Security
  • 20051128 INM Telcon: Doug e-mailed Glenn - We need the info Before phoenix
  • 20060112 PHX WGM: Addressed in Security.

== ITEM: 967 == Opened: 13-Sep-05 Old Item: 0 Security TC is requested to read WS security specification and provide guidance and suggestions related thereto.

• 13-Sep-05 , Glenn Marshall , New , Security
  • 20050913 WGM: New
• 28-Nov-05 , Glenn Marshall , New , Security
  • 20051128 INM Telcon: Doug e-mailed Glenn - We need the info Before phoenix
• 20060110, Glenn Marshall , open , Security
  • 20060110 InM WGM Phoenix: Has been read, guidance has not yet been provided.

== ITEM: 975 == Opened: 14-Sep-05 Old Item: 0 Add Religious affiliation codes to 396

• 14-Sep-05 , Tony Julian , New , v2 Ch2
  • Add Religious affilition codes to table 396
• 14-Sep-05 , Ted Klein , Open , v2 ch2
  • Will mail codes to tony Julian
• 28-Nov-05 , Tony Julian , Closed , v2 ch2
  • 20051128 INM Telcon: Content will be in the V 2.6 Ballot

== ITEM: 976 == Opened: 07-Oct-05 Old Item: 0 CNE/CWE 2.7

• 14-Sep-05 , Doug Pratt , New , V2 Cp2a
  • MMS Doug Pratt/Sandy Stuart that the joint working group encourage Doug to submit the stronger text for version 2.7. 11-0-1
• 28-Nov-05 , Doug Pratt , New , V2 Cp2a
  • 20051128 INM Telcon: Doug will submit 2.7 Proposal

== ITEM: 1004 == Opened: 03-Oct-05 Old Item: 0 20051003: Post Project Scope for Data Types Abstract and related documents XML ITS DT and UML.

• 03-Oct-05 , Grahame Grieve , New , ITS
  • 20051003: Post Project Scope for Data Types Abstract and related documents XML ITS DT and UML.

20051114: open, deferred to May ballot

• • 20060112 PHX WGM: No change

== ITEM: 1005 == Opened: 03-Oct-05 Old Item: 0 20051003: Prepare RFI for Data Types Abstract

• 03-Oct-05 , Grahame Grieve , New , Data Types
  • 20051003: INM Telcon: Prepare RFI for Data Types Abstract. Needs to be approved and posted by Oct 17.

• Open, deferred to may ballot
• 20060112 PHX WGM: No change

== ITEM: 1006 == Opened: 03-Oct-05 Old Item: 0 20051003: Prepare RFI for XML ITS Data Types

• 03-Oct-05 , Grahame Grieve , New , XML ITS
  • 20051003: INM Telcon: Prepare RFI for XML Its Data Types. Needs to be approved and posted by Oct 17.

• 20051114: Open, May ballot
• 20060112 PHX WGM: No change

== ITEM: 1007 == Opened: 03-Oct-05 Old Item: 0 20051003: Prepare RFI for UML

• 03-Oct-05 , Grahame Grieve , New , UML
  • 20051003: INM Telcon: Prepare RFI for UML. Needs to be approved and posted by Oct 17.

• 20051114: Open, deferred to may ballot
• 20060112 PHX WGM: No change

== ITEM: 1008 == Opened: 03-Oct-05 Old Item: 0 20051003: Post UML reconciliation package for May 2005 ballot.

• 03-Oct-05 , Grahame Grieve , New , UML
  • Post UML reconcillation Package for May 2005 ballot
• 20060112 PHX WGM: No change

== ITEM: 1009 == Opened: 03-Oct-05 Old Item: 0 20051003: Request withdrawal of negative votes against UML May 2005 ballot.

• 03-Oct-05 , Grahame Grieve , New , UML
  • 20051003: INM Telcon: After Reconciliation Package is posted, need to officially request voters to withdraw negative votes by November 14.
• 20060112 PHX WGM: No change

== ITEM: 1015 == Opened: 10-Oct-05 Old Item: 0 20051010: INM Telcon: Follow-up with Vocab on proposal 438 to add new values to table 0396 to support ePrescribing proposal.

• 10-Oct-05 , Tony Julian , New , Vocab
  • 20051010: INM Telcon: Follow-up with Vocab on proposal 438 to add new values to table 0396 to support ePrescribing proposal.
• 10-Oct-05 , Tony Julian , Open , Vocab
  • 20051011: E-mail sent " Colleagues: Do you wish to add these values to table396 in V2.6 to support ePrescibingproposal" including proposal 438.

ITEM: 1021

Opened: 20051031

Need to add attribute-level descriptions to HMDs in MFMI Release 2. Created as part of reconciliation of MFMI R1 M1.

• 20051031, René Spronk, open
  • Will remain open until MFMI R2 goes out for ballot again

ITEM: 1025

Opened: 20051114

Prefaces at Topic Level, Pubs issue, need to take this up with Pubs. Results from MCCI R2 C1 ballot rec. item 134.

• 20051114, Tony Julian, open
  • Propose to pubs to have preface at the topic level, instead of just having a preface at the domain level. If one has a varied range of Topics it makes no sense to have all preface comments at the domain level.
• 20060113 Tony Julian, open, pubs
  • 20060113 WGM pubs will consider. Supported by pharmacy.
• 20060508 WGM San Antonio, open
  • 20060508 WGM San Antonio: Ballot item in PFG ballot. Follow the resolution of that.

ITEM: 1027

Opened: 20051129

Fix Escape Character reference to v2 ED data type, discovered issue, from e-mail from Alberto Sáez Torres

• 20051129, Tony Julian, New
  • Page 2-13 , in Figure 2-1. "Delimiter values" The paragraph: "Escape character for use with any field represented by an ST, TX or FT data type, or for use with the data (fourth) component of the ED data type." Should say (in my opinion) "?or for use with the data (fifth) component of the ED data type"
• 20051129, Tony Julian, V2
  • Research indicates that this has been wrong since the figure was included. I suggest that this is a technical correction - From Substantivity Guide: Technical corrections that implement the original intent of the committee. For example, if a committee meant to add an attribute to one segment, and it was mistakenly added to another; this can be fixed.
  • E-mail sent to INM and ARB lists to solicit opinion

ITEM: 1028

Opened: 20051129

Change v2 maximum length to be non-normative, suggested by an e-mail from Alberto Sáez Torres

• 20051129, Tony Julian, New

In Chapter 2.5.3.2 "The maximum length is not of conceptual importance in the abstract message or the HL7 coding rules. The length of a field is normative." Should say "..The length of a field is not normative." (In my opinion)

• 20051129: email response from J Larson:
  • I believe it would be a substantive change to insert the word NOT since the ARB has ruled that length changes are substantive. As we know, not everyone has agreed with this ruling, but it is the one we need to live with.
• 20051129, Tony Julian, V2
  • Research indicates that the text 'The length of a field is normative' has been in the standard since 2.3. I will communicate with "Older" members of INM/CQ to gather their understanding.
  • E-mail sent to INM and ARB lists to solicit opinion.
• 20060104: Joann Larson (an older member of InM)
  • I would say that this is a moot point at present because InM approved proposal #435 regarding the removal of "maximum length" from the chapters at the San Diego WGM 20050916 by a vote of 6-0-1. Length will be addressed in chapter 2B and in implementation specs. In v.7 we will be balloting this proposed change.

ITEM: 1029

Opened 20051129 from e-mail from Alberto Sáez Torres

In the Data Type Chapter, the components table for XTN (Extended Telecommunication Number) doesn't correspond with the text description. Page 2-239.

• 20051129, Doug Pratt, V2
• 20060104: J Larson. The component table and narrative are correct in v.6. There was a formating/numbering problem in v2.5. Component 5 should have been "Country", but it inadvertently got embedded in the note for compoent 4. Is this ready to be closed or should we consider noting an erratum for v2.5? Email sent to A Torres.

ITEM: 1030

Opened: 20051129

Change cardinality of MSG Data Type in v2.XML specification, discovered item, from e-mail from Alberto Sáez Torres

• 20051129, Tony Julian, New
  • In the MSG data type description (message type, used in MSH-9) it is said that all the components (message code, message trigger, message sctructure) are required, but the schema marks all of them as optional.

So, the schema should be change from:

<xsd:complexType name="MSG">
 <xsd:sequence>
   <xsd:element ref="MSG.1" minOccurs="0" maxOccurs="1"/>
   <xsd:element ref="MSG.2" minOccurs="0" maxOccurs="1"/>
   <xsd:element ref="MSG.3" minOccurs="0" maxOccurs="1"/>
 </xsd:sequence>
</xsd:complexType>

To :

<xsd:complexType name="MSG">
 <xsd:sequence>
   <xsd:element ref="MSG.1" >
   <xsd:element ref="MSG.2" />
   <xsd:element ref="MSG.3" />
 </xsd:sequence>
</xsd:complexType>

• 20051129, Tony Julian, V2
  • pending further information
• 20051129, Alberto Sáez Torres
  • Actually, the MSG-data type is described in section 2.A.44 of Chapter 2A, Page 2-175, but the error is located in the XSD and DTD files for Version 2.5. The XSD affected file is “datatypes.xsd” and the DTD file is “datatypes.dtd”. This is the reason why I’ve CC-ed this message to the XML list.
  • (According to the MSG data type, the line from datatype.dtd): <!ENTITY % MSG "(MSG.1?,MSG.2?,MSG.3?)"> Should be changed (in my opinion) to <!ENTITY % MSG "(MSG.1,MSG.2,MSG.3)">

ITEM: 1031

Opened: 20060109

Fix the InM acronym in the Mission Statement and forward to HL7 HQ. (Admin)

• 20060109, Tony Julian, new
• 20060508 WGM San Antonio, open
  • 20060508 WGM San Antonio: Tony will send updated copy today.

ITEM: 1032

Opened: 20060109

Added item to update the InM DMP (Phoenix MON Q1) and forward to HL7 HQ. (Admin)

• 20060109, Tony Julian, new
• 20060508 WGM San Antonio, open
  • 20060508 WGM San Antonio: Tony will send updated copy today.

ITEM: 1033

Opened: 20060109

Proposal 965 – verify with MNM how this is a legal construct. (MFMI)

• 20060109, Robert Grant, new

ITEM: 1035

Opened: 20060109

Can a new use-case (although in scope of the domain) be brought forward in the form of a line-item, and be grounds for a negative line-item ? Or should a proposal be brought forward ? (Procedural)

• 20060109, Joann Larson, new
  • 20060109 WGM Discussion: PIC Issue ? Does this depend on the level of the ballot being commented ? Risk that the cycle goes on forever. Acceptable to make a use-case suggestion (for things that are missing, use-cases that are not covered) as an affirmative line-item.
• 20060324, Joann Larson, open
  • 20060324 Email from Larson to PIC: I have been tasked to bring the following question from InM to PIC:

"Can a new use-case (although in scope of the domain) be brought forward in the form of a line-item, and be grounds for a negative line-item ? Or should a proposal be brought forward ?" It is not clear which committee is the best committee to consider this question. We believe it is PIC, but we may be wrong. I do not recall anything in the Bylaws or PnP that addresses whether or not it is permissible to negatively ballot a document, or section of a document, where the balloter believes documentation is missing or incomplete. I suspect the thing to look at is what options the committee has for handling the line item rather than whether or not it is permissible for the balloter to submit it. I have not checked recently, but the ARB substantivity guide did at one time address whether or not it was substantive to fix incomplete content or add content where it is needed but missing. I don't know if one can extrapolate anything from that or not. The argument in InM is as follows: "The simple reason is that one can't bring forward a "proposal" in the form of a negative line-item, it kills the balloting process. " Balloter's response: If the purpose of putting something out for ballot is not to allow someone to say: Hey, you've missed a very important use case and you can't go forward with this without taking this use case into accound, then I don't know what balloting is for.

Imagine that a domain has gone to membership ballot, and someone creates a negative line-item to state that "the model doesn't cover use-case X". Ok, we accept it, add a bit of model, which causes a backwards compatible change, so we have to go back to committee level. Once we're back at membership the next proposal-disguised-as-a-line-item shows up. from a process issue this is uncontrollable. So this MCCI line-item has been declared "not related" for purely procedural reasons only, we have requested that a proposal be brought forward instead of the line-item. No, I'm sorry, but that is EXACTLY the way balloting is supposed to work. That's the way it has worked for the 8 1/2 years that I have been involved in HL7 balloting. And it has worked quite well, thank you. Does PIC have thoughts on this matter?

• 20060508 WGM San Antonio:
  • We think this is on the PIC agenda. Rene is attending this Thursday.
• 20060511 Larson, open, Late entry of email response
  • 20060327 Email received from Mead Walker and Ed Hammond indicating that this item should be reviewed by the ARB.
• 20060511: PIC WGM: There is already a statement on this. ANSI doesn’t require us to do committee level ballor reconciliation, that’s an HL7 internal rule. Bylaw 14.06.03.02 states that things can be declared as out of scope. Committee can decide that something is out of scope (even if it is in scope of the project plan) as long as one includes it in a future release.
• 20060512: INM WGM Close.

ITEM: 1050

Opened: 20060313

Send pubs documentation structure (sequence of sections) to Miroslav Koncar, for restructuring of the ATS document

• 20060313, Joann Larson, new
• 20060313, Larson: email sent to Miroslav as follows: The current Publishing Facilitator's Guide can be found on the v3 Ballot site under Background Documents.

The section of the ATS that is not consistent with the PFG is the Preface. See section 9.3.

The Preface is to be "numbered" and labeled as follows: i. Notes to Readers ii. Acknowledgements iii. Changes From Previous Release

The Overview requirements appear to have gotten muddled since I wrote this ballot comment last summer. The PFG shows an inconsistency between section 9.4 and the model in section 1 and 1.1. When I questioned Helen Stevens about the correct format last summer, she gave me the model as it appears in 1 and 1.1. Given the current discrepancy I believe it is better to not make any format change to the Overview until the PFG stabilizes.

In short, this line item should probably be disposed of as Persuasive with Mod. Fix the Preface, but leave the Overview alone until such time as there is a clear statement of proper format.

• 20060324: larson: email sent to Miroslav stating: The Publishing Facilitator's Guide has been updated so that the instructions on how to format the Overview section are clear and consistent. There is now a section 9.4.1 which reads as follows:

"The Overview’s first sub-section SHALL be entitled “Introduction and Scope” a this section SHALL contain a description of the Document at a minimum sufficient for a person unfamiliar with the work to understand the document’s business, scope and relationship with HL7. The Introduction and Scope section SHALL also explain the need for a Specification."

The Publishing Facilitator's Guide is in ballot in the May 2006 ballot cycle as an informative document. Pubs would appreciate any feedback you might have if you care to comment on it.

ITEM: 1051

Opened: 20060113

Find out the San Antonio Hotel has wireless in meeting rooms

• 20060113 co-chairs, new, organizational
  • 20060113 WGM: Find out the Hotel has wireless in meeting rooms – check with Lillian and hotel if need be.
  • 20060325 Rene: the hotel has wireless in the sleeping rooms, but uses a different network for the meeting rooms. There is no guarantee that one will be able to pick up the sleeping room network in the meeting rooms. HQ has organized wireless access in the main plenary session meeting room. I have asked HQ what it would cost to add 1 meeting room, and indicated that we realize it would not be paid by HL7. The TSC list has been notified of the situation, which will hopefully lead to a motion by the TSC that they see internet access in the meeting rooms as an absolute requirement for future WGMs.
  • 20060414 Rene: charge is $7K for 1 room for 1 week. HQ is seeking a $10K sponsor for providing wireless to all non-plenary-rooms.

ITEM: 1052

Opened: 20060113

Review status of Java SIG

• 20060113, co-chairs, new, organizational
  • 20060113 WGM: Contact JAVA SIG re meeting/accountability. Might be a project instead a SIG?
• 20060407, co-chairs, open, organizational
  • The primary objective of the Java SIG as stated in its mission is "This group will define application programming interfaces (APIs) to HL7 version 3 artifacts for the Java platform."
  • The Java WGM Minutes of January 2006 state: "The general purpose of the the javaSIG meetings at the HL7 WGM meetings is to introduce new developers to our API. Our API which has been under development since 2002 has numerous features which constitute the infrastructure for any Java based HL7 V3 applications."
  • From the September 2005 WGM minutes "The purpose of our meeting was to introduce our API to new potential users and developers. [..snip..] We spent no time on the past history of the API but rather explained the features: [etc.]"
  • The last substantive uploaded document of the Java SIG was in September 2004.
  • Relevant Bylaw 9.02.05 SPECIAL INTEREST GROUP DISSOLUTION – The Board of Directors shall consider dissolution of a SIG if: [..snip..] The objectives of the SIG have been achieved.
• Dissolve SIG and create a project under Education(?)/Tooling(?) or Implementation(?)
• 20060410, co-chairs, open, organizational
  • Java SIG will give an update FRI Q1 in San Antonio. Any future actions to be coordinated during/after that meeting.

ITEM: 1053

Opened: 20060113

Joint work item for use of digital signature in control act wrapper

• 20060113 Rene, new, security
  • 2006013 WGM: Joint work item for use of digital signature in control act wrapper

ITEM: 1054

Opened: 20060410

Synchronize use of conformance modal verbs with Publishing Facilitator's Guide

• 20060410 Joann L, new, Admin*
  • 20060410: Need to go over InM ballot domains for proper capitalization of conformance modal words SHALL, SHOULD, MAY.

ITEM: 1055

Opened: 20060108 Fix InM acronym in Mission Statement

• 20060109 WGM Phoenix: Added item to fix the InM acronym in the Mission Statement and forward to HL7 HQ.
• 20060507: Tony Julian, e-mail sent to HQ. to fix the problem.

ITEM: 1056

Opened: 20060108 Forward updated Decision making practices to HQ

• 20060109 WGM Phoenix: Added item to update the InM DMP and forward to HL7 HQ.
• 20060109: Updated on HL7
• 20060507: Email sent to HQ to correct link to DMP

ITEM: 1057

V2 Datatype CNN

• 20051129: e-mail from Alberto Sáez Torres who wrote:

5) Page 2-138 Section 2.A.9.9. Data type CNN (composite ID number and name simplified) In this element there are some references to a data type "CNS", which in my opinion is the “CNN” data type

• • 20060109 InM WGM: Doug will examine this

ITEM: 1058

20060104 Check accuracy of 3rd example for NA data type D Pratt

• 20051129: e-mail from Alberto Sáez Torres who wrote:

6) Page 2-175 Section 2.A.45 P. Data type NA (Numeric Array)

The first component is declared as “REQUIRED” (field OPT of the components table) but in the 3º example, it’s shown as non-present (|^2^3^4~5^^^8~9^10~~17^18^19^20|))
¿This is an error in the example, the OPT or in my understanding?

• 20060109 InM WGM: Doug will examine this

ITEM: 1059

V2.7 Cleanup the escape sequence language Frank Oemig

• Change the escape usage language.

ITEM: 1060

was Item 32 re: Dynamic Discovery Message - moved responsibility to MnM

• 20050127: INM WGM: ask the Conformance SIG to work on a dynamic discovery message for supported features by the receiver (profile ids, application roles, interactions, responseModeCodes)
• 20060508: InM WGM Refered to MnM

ITEM: 1061

V2.6 Add event type R25 to Table 0003 in v2.6 as a technical correction.

• 20060109 InM WGM: Add event type R25 to Table 0003 in v2.6 as a technical correction.
• 20060508 InM WGM: Done in V2.6 sent for publication.

ITEM: 1062

ask implementsr if anybody is actually using QueryByparameter.ResponseElementGroupId

• 20060508, INM co-chairs, new, MCAI
  • Plan is to remove this attribute, as it causes problems with the dynamic model, especially Receiver Responsibilities.

ITEM: 1063

Opened: 20060508

Determine what kind/type of vocab used within the datatype specs should be subject to harmonization and/or ballot time fixing.

• 20060508, new, Grahame, Abstract Data Types
  • There have been DT proposals (+vocab used within DT) during harmonization. Normative DT spec, methodology changes lead to new releases of DT spec. Changes to vocab may need to be more flexible (e.g. done at harmonization, be applicable to last normative spec) than structural DT changes. Only certain vocabs, e.g. compression method, UCUM units, mediatype, currency. Name part type is NOT in this category and is fixed at ballot time.

ITEM: 1064

Opened: 20060508

formally document updatemode/auditing methodology in the abstract DT spec.

• 20060508, new, XML SIG, Abstract data types

ITEM: 1065

Opened: 20060508

Extend proposal 971 by Pharmacy SIG requirement, and to check moodCodes

• 20060508, Michael van Campen/Rene, new, COMT
  • 20060508: new action item created as result of formal approval of 971.