7.0 Document Updates

[1] HITSP anticipates that HITSP Data Elements will eventually become a separate HITSP publication maintained jointly by the respective HITSP Domain Technical Committees.

[2] Note that the spelling of OrganisationName in this example is based upon exactly what is written in the standard.

[3] As of the date of this publication HL7 is presently engaged in the development of a set of business requirements for a template registry, which members of HITSP have also been participating in. There is a great deal of cross-fertilization going on in this project, but as of today, there are no template registries currently in use. AHRQ-USHIK has captured some of the template metadata in its data element registry, and will be working with HITSP and other member SDOs to develop a template registry. PHIN-VADS has indicated that they will be developing a template registry for CDA templates describing population health and biosurveillance.

[4] If a template uses value set 10 in one definition, and then uses value set 11 in a new definition, this is a change in value set identity.

[5] For example, C48 and C84 describe constraints for two different document subtypes within the component.

[6] The OIDs for these templates will start with 2.16.840.1.113883.3.88.11, and will be followed with the IS number, and the subset sequence number in the IS where it was defined.