1. Published Name of the Standard for which request is being made 2. Standards Material/Document 3. Date of Request 4. Use Period 5. Reason for extension, timeline, and actions 6. Original Publication Date 7. End date of the current STU period 8. Length of the requested extension 9. Review Process 10. HL7 Work Group making this request and date 10a. Requesting WG Date 11. URL of approval minutes 12. HL7 Product Management Group 12a. Management Group Date of Approval 13. URL of approval minutes 14. Is the artifact ready for final publication? 15. If not ready, please describe remaining steps. 16. Tool name used to produce the machine processable artifacts in the IG 17. The name of the “IG artifact” within the context of the above mentioned tool. 18. Balloted Name of the standard for which request is being made 19. Requested name for published standard 20. If CMET, list IDs balloted 21. Project Insight Number 22. Document Realm 23. Ballot cycle in which the document was successfully balloted 25. Affirmative 26. Negative 27. Abstentions 28. Not Returned 29. Total in ballot pool 30. Date on which final document/standards material was supplied to HQ 31. URL of publication material/ SVN repository 32. Publishing Facilitator 33. Special Publication Instructions 34. URL of ballot reconciliation document 35. Has the Work Group posted its consideration of all comments received in its reconciliation document on the ballot desktop? 36. Substantive Changes Since Last Ballot? 37. Product Brief Reviewed By 38. Date Product Brief Reviewed 39. Has the Product Brief changed? 40. Family 41. Section 42. Topic 43. Please Describe the Topic 44. Product Type 45. Parent standard 46. Parent Standard Status 47. Update/replace standard 48. Common name/search keyword 49. Description 50. Stakeholders 51. Vendors 52. Providers 53. Benefits 54. Implementations/Case Studies 55. Development Background
HL7 Terminology
Informative
Feb 12, 2023
TSMG
No
Complete generation of release after content freeze date, planned for 2/12/23.
HL7 process for publishing a FHIR IG and the tools called out by this process.
THO publication *IS* an IG (in terms of its creation controls) but it part of HL7 FHIR infrastructure as it is used by all IG publisher build operations worldwide in all the FHIR Accelerators.
Not a balloted artifact
The current name for the terminology release is simply "HL7 Terminology". The short acronym used is "THO" which stands for "terminology.hl7.org" which is the URL where it is based.
no associated project; this is an infrastructure service
UV
N/A (consensus reviews for all increment changes in the ci build)
http://terminology.hl7.org
Marc Duteau, Grahame Grieve
This is done as a 'snapshot' of the THO/UTG current build (ci build). The special tools of Grahame's insert the entries for the History Of Published Release and execute the redirects.
not a ballot item
Yes
No
No official product brief because it is not yet a product but related information below.
Cross-Paradigm
Implementation Guides
Terminology
Implementation Guide Services
One of regular periodic updates to the HL7 Terminology.
THO UTG
Not a standard. Terminology content as infrastructure to all HL7 artifacts using terminology.
Other (specify in text box below)
Other (please specify)
Other (specify in text box below)
Single source of machine-readable content for all HL7 terminology used by everyone doing HL7.
Ease of single point of access by all stakeholders, all developers, all vendors, and all providers needing to lookup, reference, and use HL7 Terminology.
Overview
Content Tools
Apps