This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "V3 Publishing ConCall Minutes 20081210"

From HL7Wiki
Jump to navigation Jump to search
 
Line 10: Line 10:
 
===Issues on Normative Edition 2009 Publishing===
 
===Issues on Normative Edition 2009 Publishing===
 
====Change of ActClass code ENTRY to GROUPER====
 
====Change of ActClass code ENTRY to GROUPER====
When the latest Vocabulary changes (from several cycles back) were implemented, ActClass code "ENTRY" was retired, and replaced with code GROUPER, for the same concept.  Because of this substitution, RoseTree does not display the retired code.  The code is retired, but the concept rmains valid with the new code.
+
When the latest Vocabulary changes (from several cycles back) were implemented, ActClass code "ENTRY" was retired, and replaced with code GROUPER, for the same concept.  Because of this substitution, RoseTree does not display the retired code.  The code is retired, but the concept remains valid with the new code.
  
Concern was raised that this may cause the schemas to fail to validate for the desiogns that had used the previous code, and were wating for the update before changing. It was agreed that the preferred course would have been to deprecate the Code ENTRY.  However, it is thought that only a single artifact uses this code, and it has not YET been published as Normative.  Therefore, a simpler approach is to make this change as a technical correction prior to publication, since both codes point to the SAME concept, and the old code was not used to create the formal name for the class.
+
Concern was raised that this may cause the schemas to fail to validate for the designs that had used the previous code, and were waiting for the update before changing. It was agreed that the preferred course would have been to deprecate the Code ENTRY.  However, it is thought that only a single artifact uses this code, and it has not YET been published as Normative.  Therefore, a simpler approach is to make this change as a technical correction prior to publication, since both codes point to the SAME concept, and the old code was not used to create the formal name for the class.
  
 
Beeler agreed to test other designs for use of this code. (This test was run shortly after the conference call, and the string "ENTRY" does NOT appear as a code anywhere except the affected Lab design (POLB_HD004000UV01) and the Vocabulary coremif (where it shows as retired).  The string "ENTRY" does appear in a textual discussion in CMET COCT_MT480000UV but here it appears as part of a discussion on the elements of openEHR.)  
 
Beeler agreed to test other designs for use of this code. (This test was run shortly after the conference call, and the string "ENTRY" does NOT appear as a code anywhere except the affected Lab design (POLB_HD004000UV01) and the Vocabulary coremif (where it shows as retired).  The string "ENTRY" does appear in a textual discussion in CMET COCT_MT480000UV but here it appears as part of a discussion on the elements of openEHR.)  

Latest revision as of 21:15, 17 December 2008

Return to Publishing Committee
Minutes of Recent Publishing Conference Calls

Wednesday, December 10, 2008 -- 4:00 PM Eastern

Present

Beeler, Harding, Kreisler, Lloyd, Seppala, Stechishin, Savage, Madra

Agenda

Issues on Normative Edition 2009 Publishing

Change of ActClass code ENTRY to GROUPER

When the latest Vocabulary changes (from several cycles back) were implemented, ActClass code "ENTRY" was retired, and replaced with code GROUPER, for the same concept. Because of this substitution, RoseTree does not display the retired code. The code is retired, but the concept remains valid with the new code.

Concern was raised that this may cause the schemas to fail to validate for the designs that had used the previous code, and were waiting for the update before changing. It was agreed that the preferred course would have been to deprecate the Code ENTRY. However, it is thought that only a single artifact uses this code, and it has not YET been published as Normative. Therefore, a simpler approach is to make this change as a technical correction prior to publication, since both codes point to the SAME concept, and the old code was not used to create the formal name for the class.

Beeler agreed to test other designs for use of this code. (This test was run shortly after the conference call, and the string "ENTRY" does NOT appear as a code anywhere except the affected Lab design (POLB_HD004000UV01) and the Vocabulary coremif (where it shows as retired). The string "ENTRY" does appear in a textual discussion in CMET COCT_MT480000UV but here it appears as part of a discussion on the elements of openEHR.)

With this knowledge, Beeler will seek John Quinn's OK of this as a Technical Correction and Austin will change the code in the Lab design.

Managing SVN Submissions for NE2009

The people who are submitting content using SVN, would like to follow the same pattern for the NE2009 content. Unfortunately, however, we do not yet have an established pattern and practice of "tagging" submissions to distinguish between Ballot and Edition content.

Therefore, we agreed to implement a set of temporary sub directories under the "domains" directory in the input files. These will be named the same as the ballot domain, except that the opening two letters "uv" will be replaced with the letters "ne".

Moreover, Beeler will undertake to pre-populate the sub directories in SVN, and provide the content from the prior Normative Edition for reference and amendment by the developers. He will also attempt to move the appropriate CMET static model designs into the directories for those groups.

The following domains will be established in this fashion: nelb, nepa, nepm, nerr, nerg, nesp

Remaining meetings in 2008

Because the regularly scheduled Publishing conference calls will fall on Christmas Eve and New Year's Eve, the scheduled meeting one week from today (on December 17) we the last meeting for 2008. We will use that meeting to focus on planning for the agenda for the January Working Group Meeting in Orlando Florida.

Co-Chair Absence

Dick Harding noted that he will be unavailable to meet from Christmas through to about February 15, 2009.

Adjourned at 3:40PM