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

2015 03 27 Minutes - CDA R2.1 Project

From HL7Wiki
Jump to navigation Jump to search



  • Austin Kreisler
  • Benjamin Flessner
  • Calvin Beebe
  • Kathleen Connor
  • Vinayak - Cerner (VK)
  • Rob Hausam
  • Andy Stechishin
  • KC

Minutes / Notes

  1. Current Agenda
    1. Review DPROV CDA R2.1 Wish List / Participation Functions and Role codes
      1. not on Entity
      2. ok on role
      3. role confidentially code % Confidentially code on clinical statement - review 2.07
      4. Needs some modeling assessment.
      5. -
      6. Backwards compatility change in RIM
        What we mean by backwards and forwards compatibility
        Instances of documents old and new
        Receiver old and new - expected to process
      7. another backwards compatibility question
      8. add attributes / Amend the RIM definition - participation functions is not fluff , it is really important. - Maybe an IG assertions
      9. Need to add to entry and section where ever there is a device for Identifiers.
        Backwards Compatibility and Substantivity
        It is important to distinguish between the distinct but related concepts of interversion compatibility and substantivity.Substantivity is significant because of its role in the balloting process. Our rules for substantivity are based on the need to ensure that changes that are made to the standard are appropriately subjected to ballot review. For this reason, both additions and deletions from the standard are treated as substantive. As a general matter, any change which changes semantics is substantive. Interversion compatibility, on the other hand, is significant because as a way to recognize the significant cost of upgrading an installed interface from one version of the standard to a subsequent version. The rules governing interversion compatibility are centered around two notions: a) Old receivers receiving new messages should be able to continue receiving messages without error, b) New receivers should be able to understand old messages. In order to reduce this cost, HL7 V3 has introduced rules to limit the introduction of changes causing interversion compatibility problems. Those rules, which do not prevent the introduction of new features to the standard, specify that, before a feature can be removed, it must be listed as deprecated within an intervening Normative Edition of Version 3. As a practical matter, all changes that violate interversion compatibility rules are substantive. However, the converse is not true. Many changes which do not violate interversion compatibility may, nevertheless, be substantive.
    2. Discuss the communication plan for RIM 2.07a Project
    3. Open Topics