Skip to end of metadata
Go to start of metadata

Publication Request

Publication Request

1. Published Name of the Standard for which request is being made

2. Standards Material/Document


3. Date of Request

Apr 18, 2019

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

Orders & Observations

10a. Requesting WG Date

11. URL of approval minutes,+2019

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

HL7 Version 3 Domain Analysis Model: Specimen, Release 2

19. Requested name for published standard

HL7 Domain Analysis Model: Specimen, Release 2

20. If CMET, list IDs balloted

21. Project Insight Number


22. Document Realm


23. Ballot cycle in which the document was successfully balloted


24. Results of that ballot (following reconciliation activities):

24. Results of that ballot (following reconciliation activities):

(not needed for errata, STU extension, or unballoted STU update)

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

Apr 19, 2019

31. URL of publication material/ SVN repository

32. Publishing Facilitator

33. Special Publication Instructions

Both the EA file and the document (which has the model view integrated as jpeg) should be published.

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

HL7 O&O WG call on 2019-04-18

38. Date Product Brief Reviewed

Apr 18, 2019

39. Has the Product Brief changed?

Product Brief

Product Brief

40. Family


41. Section

Clinical and Administrative Domains

42. Topic


43. Please Describe the Topic

44. Product Type

45. Parent standard

46. Parent Standard Status

47. Update/replace standard

HL7 Domain Analysis Model: Specimen, Release 1

48. Common name/search keyword

Specimen DAM, Specimen Domain Model

49. Description

This specification is the second release of a Domain Analysis Model for Specimen, documenting the conceptual information requirements for use cases provided by Clinical Genomics, Anatomic Pathology and Public Health Laboratories, the harmonization with the Biomedical Research Integrated Domain Group (BRIDG) model as well as the business needs of the current v2 and v3 specimen models.



These are categories of potential users, implementers, or other interested parties such as those that are indicated on the Project Scope Statement under “Stakeholders/Vendors/Providers”. Select those that are applicable, or suggest others:

50. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Standards Development Organizations (SDOs)

51. Vendors

EHR, PHR, Health Care IT, Lab

52. Providers

Clinical and Public Health Laboratories Local and State Departments of Health Healthcare Institutions (hospitals, long term care, home care, mental health)

53. Benefits

 Creates a unified approach to specimen related attributes across various use cases
 Enumerates the related data elements applicable to specimen related use cases from different areas of laboratory functions
 Enables a starting point for implementers / vendors to consider data elements needed to cover different healthcare functions
 Expanded the National Cancer Institute Life Sciences DAM to include non-living subject’s specimen

54. Implementations/Case Studies

This document is used to inform messaging solutions in v2.x as well as creating FHIR resources. It has also been mapped to DICOM elements in order to support Digital Pathology Workflows.

55. Development Background