Implementation/Conformance Meeting Minutes



Implementation/Conformance Meeting Minutes

Rio de Janeiro Working Group Meeting, May 16-20, 2010

Monday 17 May 2010, Quarter 1

Agenda

|# |Key |Description |Presenter |Action Needed |Time |

|2 | |Approval of Agenda |Frank | | |

|3 | |Announcements |Frank | | |

|4 | |Approve minutes (Atlanta) |Frank | | |

|5 | |Follow-Up Action Items |Frank | | |

|6 | |SWOT Analysis | | | |

|7 | |Other topics |Frank | | |

|8 | |Adjournment | | |10:30 |

Attendance

|Name |Organization |eMail |

|Carnahan, Lisa |NIST |lisa.carnahan@ |

|Connell-Clark, tina |NEHTA |tina.connell_clark@.au |

|Cooper, Todd |BSF/DEV WG |t.cooper@ |

|Kavanagh, Richard |NHS UK |richard.kavanagh@ |

|Martines, Sandra |NIST |smartines@ |

|McCauley, Vincent |HL7 Australia |vincent@ |

|Oemig, Frank |HL7 Germany |Frank@Oemig.de |

|Snelick, Robert |NIST |rsnelick@ |

Minor changes made to the agenda.

Follow-up Action Items

SWOT Analysis

Discussed, but no update

Other Topics

v2.7: discussion with InM about Datatype XPN and possible technical correction.

Different usage codes for sender/receiver -> Vince: does not eliminate the need of different profiles

Proposals:

1. Perhaps it makes sense to introduce a “Conformance Facilitator” for all groups

2. All documents should have a conformance section

3. IC would host conformance facilitator which would present summary of their conformance work within their WGs

Rob presented this idea to FTSD, but received very little enthusiasm from the FTSD. The group feels that this new position will not bring forward more participation in ICWG and the other groups were already overloaded with work to take on another responsibility. Rob has mentioned that ICWG has already approached to other groups, but no active feedback. It was suggested that ICWG go to the other working group and become active in this manner.

Monday 17 May 2010, Quarter 2

Agenda

|# |Key |Description |Presenter |Action Needed |Time |

|2 | |chapter 2B |Rob | | |

|3 | |Adjournment | | |12:30 |

Attendance

|Name |Organization |eMail |

|Carnahan, Lisa |NIST |lisa.carnahan@ |

|Garguilo, John |NIST |john.garguilo@ |

|Kavanagh, Richard |NHS UK |richard.kavanagh@ |

|Martines, Sandra |NIST |smartines@ |

|McCauley, Vincent |HL7 Australia |vincent@ |

|Oemig, Frank |HL7 Germany |Frank@Oemig.de |

|Snelick, Robert |NIST |rsnelick@ |

Update on v2.8

No updates on v2.8 proposals on were presented. No progress was made.

Instead Rob presented a proposal for “How to write implementation guides”. The proposal reflected the fact that many implementation guides are being written in HL7, IHE, CDC, and by other organizations. Each has their own style, terminology and interpretation of conformance. Specific points:

1. the implementation guides should be based on a template (common style)

2. easier: we need more tooling to write implementation guides, perhaps enhancing MWB, or new tools from UK or the NIST testing infrastructure project

3. Need to add explicit conformance requirements either embedded directly into the specification or as a supplement

4. Conformance requirements need to be processed (pulled out) of the document automatically by tooling

5. Need to standardize on a common format to allow for the automated tooling. This way any tool could be used to extract the conformance requirements.

6. Need to build standardize conformance section so the conformance is interpreted in the same way across implementation guides

7. Need to explicitly state the various conformance requirement and validation process

Initially, a pilot project would be developed for V2. Conversion to other standards would follow.

Rob will make formal proposal and seek to make this an HL7 project.

|# |Description |Who |History/Update |Status |Area |

| |Develop initial template (example) |Rob |Initial template |Open | |

OIDs for codesystems in v2.x?

How to assign OIDs to tables in v2.x; the OIDs are assigned to the tables, but not the values (i.e. codesystems), therefore we have to find a schema to identify the contents; it would be good to have a clear reference.

The OID should also be assigned to the header in chapter 2C.

|# |Description |Who |History/Update |Status |Area |

Monday 17 May 2010, Quarter 3

Agenda

|# |Key |Description |Presenter |Action Needed |Time |

|2 | |Testing Environment |Rob | | |

|5 | |Adjournment | | |15:00 |

Attendance

|Name |Organization |eMail |

|Carnahan, Lisa |NIST |lisa.carnahan@ |

|Garguilo, John |NIST |john.garguilo@ |

|Martines, Sandra |NIST |smartines@ |

|McCauley, Vincent |HL7 Australia |vincent@ |

|Oemig, Frank |HL7 Germany |Frank@Oemig.de |

|Snelick, Robert |NIST |rsnelick@ |

Rob presented an overview of plans for NIST testing infrastructure project. Work has begun in certain areas including IHE pre-connect-at-thon testing.



Additional resources for the project via ARRA funding will begin in the fall of 2010. An overview can be found at: . All source code and tools will be publically available.

Tuesday 18 May 2010, Quarter 1

Agenda

|# |Key |Description |Presenter |Action Needed |Time |

|2 | |RCnL: new codes |Llyod | | |

|3 | |Meaningful Use Testing |Rob | | |

|4 | |Adjournment | | |10:30 |

Attendance

|Name |Organization |eMail |

|Martines, Sandra |NIST |smartines@ |

|Oemig, Frank |HL7 Germany |Frank@Oemig.de |

|Snelick, Robert |NIST |rsnelick@ |

RCnL: new conformance codes for sender/reciever

Lloyd did not show up so that we have tabled this issue for the next meeting.

Meaningful Use Testing

Rob presented a discussion on specific profiles for meaningful use testing. He discusses the approach NIST was taken given the simple IFR criteria. How to derived conformance requirements from the IFR criteria was problematic.

Tuesday 18 May 2010, Quarter 2

Agenda

|# |Key |Description |Presenter |Action Needed |Time |

|2 | |ECCF: comments |Charlie | | |

|3 | |Adjournment | | |12:10 |

Attendance

|Name |Organization |eMail |

|Bond, Andy |NEHTA |andybond@.au |

|Carnahan, Lisa |NIST |lisa.carnahan@ |

|Lynch, Cecil |Ontoreason |clynch@ |

|Martines, Sandra |NIST |smartines@ |

|McCauley, Vincent |HL7 Australia |vincent@ |

|Oemig, Frank |HL7 Germany |Frank@Oemig.de |

|Snelick, Robert |NIST |rsnelick@ |

|Mead, Charlie |NCI |meadch@mail. |

ECCF: comments

Charlie Mead believes that ICWG should be responsible for ECCF. IC agrees but needs to become more active in this area.

ECCF is a framework for collecting artefacts for a specification.

ECCF IG: list of details being necessary for writing ECCF-compliance IG.

ECCF compliant with ISO 17000.

The work of the ECCF needs to be reviewed by IC. Some of the idea in the ECCF may be applied in the proposed “How to write IG” project. The ECCF is not specific to V3; there is no reason why the ideas shouldn’t project to V2. HL7 ECCF implementation is appropriate for Services, Messages, and Documents.

Action Items

|# |Description |Who |History/Update |Status |Area |

Tuesday 18 May 2010, Quarter 3

Canceled

Thursday 20 May 2010, Quarter 1

Agenda

|# |Key |Description |Presenter |Action Needed |Time |

|2 | |Binding Syntax |Vocab | | |

|3 | |other Project proposals |Vocab | | |

|4 | |Adjournment | | |10:30 |

Attendance (ICWG)

|Name |Organization |eMail |

|Oemig, Frank |HL7 Germany |Frank@Oemig.de |

|Snelick, Robert |NIST |rsnelick@ |

For other participants please see Minutes from Vocab.

Binding Syntax

Updated project scope statement for vocabulary binding

• see core principles 5.2.3.1 for further information

• guidance is usually not considered normative

• compare with MIF: should be in sync

• will be informative

• schedule conf calls to draft an outline

• targeting January 2011 ballot

RCnL

New section to RCnL for terminology usage: Beverly will provide first wording

Core Principles

Update on Core Principles for vocabulary binding

Other Business

Planning for Cambridge

Not discussed, but please see wiki:



Action Items

|# |Description |Who |History/Update |Status |Area |

Wiki

Rene has presented some means during the co-chair dinner on how to use the wiki efficiently. The use of categories may help update specific lists. Therefore, the minutes (WGM + conf.calls) and agendas should make use of it.

Action Items

|# |Description |Who |History/Update |Status |Area |

| |Introduce categories to wiki pages for ICWG: |Frank | |New + done | |

| |The agendas for this year support thi feature now.| | | | |

| |Further categoriesare prepared for minutes and | | | | |

| |conference calls. So just add to the top of the | | | | |

| |page: | | | | |

| | | | | | |

| |[[Category:IC_Minutes|IC Minutes]] | | | | |

| |[[Category:IC_Agendas|IC Agendas]] | | | | |

| |[[Category:IC_conf_calls|IC Conference Calls]] | | | | |

| | | | | | |

| |See: | | | | |

| | | | | | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download