Skip to end of metadata
Go to start of metadata

Errata:

Definition:  Errata is the vehicle by which a technical correction is published

An HL7 errata is a package of documents that conveys the application of a technical correction to one or more published versions of a standard. 

It is formalized using both : 

The CTO Errata Cover Letter  is addressed to the member who downloads/accesses the standard. 

It contains

  • The date the letter was published
  • The published formal name of the standard
  • A link to the published document/standard being referenced
  • A paragraph describing the Work Group's plan plan to apply the correction to future ballots/publications
  • A list of the change(s).
  • A manifest of the file(s) included in the package which document(s) the change(s).
  • Technical Guidance and clarification notes
  • The signature of the CTO

What to do when a specification is BAP (broken as published) (formerly technical correction)

Non-substantive technical corrections to a balloted specification published as Normative involve correcting changes that alters a document so that it says what the Work Group intended to say. It includes edits that:

  • were not made,
  • were incorrectly made
  • were inconsistently made during the editing process.

Substantive technical corrections to a balloted specification published as Normative can be made:

  • By re-balloting

Changes to a balloted specification published as STU can be made: 

  • By technical corrections and the errata process
  • By using the STU update process, whether substantive or not.
  • By re-balloting.

Changes to a balloted specification published as Informative may be made: 

  • By technical corrections and the errata process
  • By re-balloting.