Page tree

HL7 International Logo_small Publication Request of HL7 Standards Material

Standards Material/Document - check one:

 

Normative

X

STU

 

Informative

 

Errata

 

If you checked STU above, please indicate:

Number of months the Work Group wishes to have the document published as a STU e.g.: 12 months (maximum for extension),18 months, or 24  months (maximum)

12

Is this a STU Extension?

Yes

Is this an Unballoted STU Update

 

Please use this form to submit the request to the TSC.

 

 

 

 

 

 

 

 

Date of this request:

2019-02-21

HL7 Work Group making this request and date /URL of approval minutes:

PH 2/21/2019

https://confluence.hl7.org/display/PHWG/2019-02-21+Meeting+notes

Balloted Name of the standard for which request is being made :

HL7 CDA® R2 IG: Reporting to Public Health Cancer Registries from Ambulatory Healthcare Providers, R1, DSTU Release 1.1 - US Realm

If CMET, list IDs balloted:

COCT_MTxxxxxx

 

URL of Project Scope Statement or Project Insight Number:

Project Insight # 1069

 

Document Realm:

US

Ballot cycle in which the document was successfully balloted:

2014-09

 

Results of that ballot (following reconciliation activities):

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

Vote

Number

Vote

Number

 

 

 

 

Affirmative

 

Not Returned

 

Negative

 

Total in ballot pool

 

Abstentions

 

Needed for Passage

 

 

Date on which final document/standards material was supplied to HQ

2015-04-24

URL of publication material/ SVN repository and publishing facilitator:

http://www.hl7.org/implement/standards/product_brief.cfm?product_id=398

Special Publication Instructions:

 

 

If STU Update: What review process was followed and when was it approved by WG? (peer review, wiki, comment ballot)

 

If STU Extension:  reason for extension, timeline, and actions according to GOM 13.02.06.02, Extending the Trial Use Period

Reason: Guide would benefit from additional feedback from several EHR vendors that have recently started or plan to soon begin testing and/or implementation. This guide in cited in a federal regulation, the 2015 Edition Health IT Certification Criteria.

Timeline: 12 months from the expiration date

 

 


(not needed for STU extension or errata)

URL of ballot reconciliation document:

 

 

(not needed for STU extension or errata)

Has the Work Group posted its consideration of all comments received in its reconciliation

document on the ballot desktop? 

 

Yes

 

No

Substantive Changes Since Last Ballot?

 

Yes

 

No

 

(not needed for STU extension or errata)

Cross Artifact Consistency - for RIM-Based Standards (not Implementation Guides), check all that apply:

 

Standard uses CMETs from HL7-managed CMETs in COCT, POCP (Common Product) and other domains

 

Standard uses harmonized design patterns (as defined through RIM Pattern harmonization process)

 

Standard is consistent with common Domain Models including but not limited to Clinical Statement, Common Product Model and "TermInfo"

 

 

 

Please provide the following information for the publication of the product brief:

[Note: Product brief is unchanged]

 

Family : (select one)

  • Arden
  • CCOW
  • CDA
  • Education
  • EHR
  • V2
  • V3

 

 

Section : (select those that are applicable:)

  • Clinical and Administrative Domains
  • EHR Profiles
  • Implementation Guides
  • Rules and References
  • Education and Awareness

 

 

Category : (select those that are applicable:)

e.g. briefs under Clinical and Administrative Domains

e.g. briefs under Rules and References

Cardiology

CCOW

Care Provision

Data Types

Clinical Genomics

Decision Support

Clinical Statement

Encoding Syntax

Community-Based Health

Methodology Specifications

Decision Support

Security and Privacy

Domain Analysis Model

Services

Financial Management

Specification Errata

Functional Profile

Standard Reference Materials

HHSFR

Structures

Laboratory

Terminology

Materials Management

Transport Specifications

Medical Records

 

Patient Administration

 

Patient Care

 

Patient Referral

 

Personnel Management

 

Pharmacy

 

Public Health

 

Regulated Products

 

Regulated Studies

 

Scheduling

 

Services

 

SPL

 

Other: (Please describe)

 

Other: (Please describe)

 

 

 

Parent standard : (e.g. the standard to which an implementation guide applies)

 

 

 

Update/replace standard : (e.g. is this a STU update, or is there an R1 specification which an R2 publication updates or replaces) – Please specify if this publication has a replacement, supplemental or addendum relationship to a prior standard or STU:

 

 

 

Common name/search keyword : Please specify if the publication is known by a common name internally to the Work Group or a specific search term/acronym should be provided to help users find the product.

Common Names/Aliases:

Search Keywords:

 

 

 

Description : This is typically a short paragraph summarizing the use and intent of the standard, such as would be found in an overview paragraph in the published specification.


 

 

 

Targets : 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:

Stakeholders

Vendors

Providers

Clinical and Public Health Laboratories

Pharmaceutical

Clinical and Public Health Laboratories

Immunization Registries

EHR, PHR

Emergency Services

Quality Reporting Agencies

Equipment

Local and State Departments of Health

Regulatory Agency

Health Care IT

Medical Imaging Service

Standards Development Organizations (SDOs)

Clinical Decision Support Systems

Healthcare Institutions (hospitals, long term care, home care, mental health)

Payors

Lab

Other (specify in text box below)

Other (specify in text box below)

HIS

N/A

N/A

Other (specify below)

 

 

N/A

 

 

 

Benefits : This section will describe the benefits the standard or its implementation provides to healthcare, information technology, interoperability and the like. This section is often difficult to compose and will require careful editing by the review group(s). Please create phrases such as

 

 

 

 

 

 

 

 

 

 

 

Implementations/Case Studies : This section would identify the known implementers of the standard, production or STU implementers, or any known adopters of the specification. Agencies or other organizations that sponsored the development of the specification could be listed here.

 

 

 

 

 

 

 

Development Background : This section may be used for additional important information beyond the short summary in the Description, such as would be found in an Introduction section, in the published specification.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Reviewed By, and Date : (i.e. the group or individuals endorsing this product brief information and the date the endorsement was approved)

 

Email this Request to lynn@hl7.org