Skip to end of metadata
Go to start of metadata

1a. Project Name

HL7 CDS Hooks: Hook Definitions

1b. Project ID


1c. Is Your Project an Investigative Project (aka PSS-Lite)?


1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU?


1e. Today's Date

1f. Name of standard being reaffirmed

1g. Project Artifact Information

1h. ISO/IEC Standard to Adopt

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

1j. Unit of Measure

2a. Primary/Sponsor WG

Clinical Genomics

2b. Co-Sponsor WG

Community Based Care and Privacy

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods


2d. Project Facilitator

Bryn Rhodes

2e. Other Interested Parties (and roles)

Isaac Vetter (implementer)
Dennis Patterson (implementer)

2f. Modeling Facilitator

Isaac Vetter

2g. Publishing Facilitator

Bryn Rhodes

2h. Vocabulary Facilitator

Robert McClure

2i. Domain Expert Representative

2j. Business Requirements Analyst

2k. Conformance Facilitator

Bryn Rhodes

2l. Other Facilitators

2m. Implementers

University of Utah
Wolters Kluwer

3a. Project Scope

This project will define individual hooks to be used with the CDS Hooks specification. See


3b. Project Need

The CDS Hooks specification itself does not define individual hooks. Instead, hooks follow a separate maturity model. When a hook reaches maturity level 5, it gets balloted through HL7. See

3c. Security Risk


3d. External Drivers

3e. Objectives/Deliverables and Target Dates

Ballot the patient-view hook definition in January 2020. Additional hook definitions will be balloted as they become mature.

3f. Common Names / Keywords / Aliases:

CDS Hooks Definitions, Hook Definitions

3g. Lineage


3h. Project Dependencies


3i. HL7-Managed Project Document Repository URL:

3j. Backwards Compatibility


3k. Additional Backwards Compatibility Information (if applicable)

3l. Using Current V3 Data Types?


3l. Reason for not using current V3 data types?

Not a V3 specification

3m. External Vocabularies


3n. List of Vocabularies

3o. Earliest prior release and/or version to which the compatibility applies

4a. Products

Guidance (e.g. Companion Guide, Cookbook, etc)

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4c. FHIR Profiles Version

4d. Please define your New Product Definition

4d. Please define your New Product Family

5a. Project Intent

Supplement to a current standard, Implementation Guide (IG) will be created/modified

5a. White Paper Type

5a. Is the project adopting/endorsing an externally developed IG?


5a. Externally developed IG is to be (select one)

5a. Specify external organization

5a. Revising Current Standard Info

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

5d. Joint Copyright


5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval.


6a. External Project Collaboration

6b. Content Already Developed

patient-view hook is at maturity level 4

6c. Content externally developed?


6d. List Developers of Externally Developed Content

6e. Is this a hosted (externally funded) project?


6f. Stakeholders

Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs), Payors

6f. Other Stakeholders

6g. Vendors

EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab, HIS

6g. Other Vendors

6h. Providers

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

6h. Other Providers

6i. Realm


7d. US Realm Approval Date

7a. Management Group(s) to Review PSS


7b. Sponsoring WG Approval Date

May 08, 2019

7c. Co-Sponsor Approval Date

May 08, 2019

7c. Co-Sponsor 2 Approval Date

7c. Co-Sponsor 3 Approval Date

7c. Co-Sponsor 4 Approval Date

7c. Co-Sponsor 5 Approval Date

7c. Co-Sponsor 6 Approval Date

7c. Co-Sponsor 7 Approval Date

7c. Co-Sponsor 8 Approval Date

7c. Co-Sponsor 9 Approval Date

7c. Co-Sponsor 10 Approval Date

7e. CDA MG Approval Date

7f. FMG Approval Date

Jul 31, 2019

7g. V2 MG Approval Date

7h. Architecture Review Board Approval Date

7i. Steering Division Approval Date

Oct 14, 2019

7j. TSC Approval Date

Nov 04, 2019


  1. Bryn Rhodes Per PMO/HQ review, the following fields need to be completed:
    HL7 Managed Project Document Repository URL


    Work Group Approval Date

    1. Trying to edit takes me to a New PSS, so I'm not sure what I'm doing wrong there. The project was approved 5/8/2019 at the Montreal WGM, Wednesday Q1 (Minutes: 2019-05-08 CDS WGM Minutes Montréal)

      I'm not sure what is meant by Lineage, I don't see a field for that?

      For the project document repository, I haven't requested that yet.

  2. Dave Hamill , okay, I made what I think are the correct changes.