Minutes: Templates WG Conference Call.

Friday, July 6,
2012 and Draft Agenda for Friday July 13, 2012 conference
call
July 6, 2012 minutes:
Attendance:
Jane Curry
Kai Heitmann
John Roberts
Mark Shafarman
Andy Stechishin

Scribe:
Mark Shafarman

Agenda for 7/13/12 conference call:

Discuss and vote on the Templates WG's formal comments to the Patient
Care proposals for using the OID extension (of the II datatype) for
computable purposes.
Report on the Templates ITS Pilot progress and status.
Discuss and plan next steps in the project.
All: continued discussion of coordination between templates and other
work groups.
All: any further experience with HingX after joining last week.
Review of to-do list from last week.

Meeting notes:
The HingX project.

Jane reported that they are testing pre-requisites (and code) for HingX
user groups, and exploring user group's best practices. They are
working towards defining registration (metadata and process) patterns
that can be implemented for identified groups of templates.
There is a separate user group for the Templates ITS project.
Kai is interested in exploring HingX uses for the DECOR projects. He
needs support for reviewers, creators, and implementers, as well as for
projects using templates. At the end of the call Jane walked him
through the HingX online processes for creating user groups for the
DECOR project.

The Templates ITS project:

Kai reported on DECOR issues: DECOR is creating two groupings of
templates for review and reuse by their users: a "Serious sandbox" and
a "Building blocks" collection. He needs to set up a registry and/or
repository for both, and will experiment with HingX in the coming
week.
There is a coordination issue with the Patient Care work group's
approach to Clinical Statement templates, as expressed by Kevin
Coonan, one of their co-chairs: it concerns the use of the HL7 v3
instance identifier (ii) datatype. This datatype has two components, the
first is an ISO OID and the second is an extension. The ISO OID
functions as a formal universal identifier for a template instance (and
its accompanying metadata), while the extension is a an arbitrary
string, that may be helpful for human readability, but is not required to
be unique, and more importantly, is not specified to be any type of
computable property either within or outside of the scope of the OID
component. The extension is also distinct from a version number. Both
the versioning and replacement paradigms for templates are defined in
the Templates Registry Business Process Analysis ballot document.
However, the Patient Care proposal would use the OID extension for
computable purposes, such as search categories. This is a limited,
single view use that is better supported by the template instance's
multiple use metadata.
Kai has offered to write up a proposal for our next meeting so that the
Templates WG can take a formal position on this matter.

Other Follow Ups to confirm or update:

1. Updating and submitting Templates Registry Business Requirements
Analysis informative document to the HL7 Ballot site. Will the
updates suggested last week be done in time for the July 22d
deadline? Jane, Corinne. (Still open)
2. John has volunteered to post the recent minutes on the website and
update the ballot site with the details on the resolution of the
single negative ballot on the January 2012 ballot of the Templates
Registry Business Requirements Mark may have some time to help
during the following week. (Still open).
3. We need to have active contacts with Patient Care. Mark has
volunteered to follow up with Kevin Coonan of Patient Care. We
also need to continue with Vocabulary and Structured Documents.
(Still open)