Skip to end of metadata
Go to start of metadata


 Show Changes

Version

1

Modifier

Anne Wizauer

Modify Date

Sep 17, 2019 15:49

1a. Project Name

HL7 CDS Hooks: Hook Definitions

1b. Project ID

1535

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

No

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

No

2a. Primary/Sponsor WG

Clinical Decision Support

2b. Co-Sponsor WG

Clinical Quality Information

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

At WGMs

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

2k. Conformance Facilitator

Bryn Rhodes

2m. Implementers

Epic
Cerner
University of Utah
Wolters Kluwer

3a. Project Scope

This project will define individual hooks to be used with the CDS Hooks specification. See https://cds-hooks.hl7.org/1.0/#hooks.

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 https://cds-hooks.hl7.org/1.0/#hook-maturity-model.

3c. Security Risk

No

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

N/A

3h. Project Dependencies

N/A

3i. HL7-Managed Project Document Repository URL:

http://github.com/HL7/cds-hook-definitions

3j. Backwards Compatibility

N/A

3l. Using Current V3 Data Types?

No

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

Not a V3 specification

3m. External Vocabularies

No

4a. Products

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

5a. Project Intent

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

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

No

5b. Project Ballot Type

STU to Normative

5d. Joint Copyright

No

6b. Content Already Developed

patient-view hook is at maturity level 4

6c. Content externally developed?

No

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

No

6f. Stakeholders

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

6g. Vendors

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

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)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

May 08, 2019

7c. Co-Sponsor Approval Date

May 08, 2019

7f. FMG Approval Date

Jul 31, 2019


1a. Project Name

HL7 CDS Hooks: Hook Definitions

1b. Project ID

1535

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

No

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

No

2a. Primary/Sponsor WG

Biomedical Research & Regulation

2b. Co-Sponsor WG

Clinical Interoperability Council

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

At WGMs

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

2k. Conformance Facilitator

Bryn Rhodes

2m. Implementers

Epic
Cerner
University of Utah
Wolters Kluwer

3a. Project Scope

This project will define individual hooks to be used with the CDS Hooks specification. See https://cds-hooks.hl7.org/1.0/#hooks.

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 https://cds-hooks.hl7.org/1.0/#hook-maturity-model.

3c. Security Risk

No

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

N/A

3h. Project Dependencies

N/A

3i. HL7-Managed Project Document Repository URL:

http://github.com/HL7/cds-hook-definitions

3j. Backwards Compatibility

N/A

3l. Using Current V3 Data Types?

No

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

Not a V3 specification

3m. External Vocabularies

No

4a. Products

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

5a. Project Intent

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

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

No

5b. Project Ballot Type

STU to Normative

5d. Joint Copyright

No

6b. Content Already Developed

patient-view hook is at maturity level 4

6c. Content externally developed?

No

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

No

6f. Stakeholders

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

6g. Vendors

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

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)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

May 08, 2019

7c. Co-Sponsor Approval Date

May 08, 2019

7f. FMG Approval Date

Jul 31, 2019






3 Comments

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

    Lineage

    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.