HL7 Project Scope Statement s6

/ Health Level Seven®, International
2013 Project Scope Statement

NOTE: To use Track Changes, turn off “protection” by clicking on (pre-MS Word 2007) Tools > Unprotect Document or (MS Word 2007 and higher) Review > Protect Document.

1. Project Name and ID

Event Publish & Subscribe Service Interface Specification Project / Project ID:

2. Sponsoring Group(s) / Project Team

Primary Sponsor/Work Group (1 Mandatory) / SOA
Co-sponsor Work Group(s) / Clinical Decision Support
Project Team:
Project facilitator (1 Mandatory) / Emory Fry, MD
Other interested parties and their roles / Craig Parker, MD; Davide Sottara, PhD
Multi-disciplinary project team (recommended)
Modeling facilitator
Publishing facilitator
Vocabulary facilitator
Domain expert rep
Business requirement analyst
Conformance facilitator (for IG projects)
Other facilitators (SOA, SAIF) / SOA: Ken Rubin, CDS: Ken Kawamoto, MD
Implementers (2 Mandatory for DSTU projects):
Cognitive Medical Systems, Inc.
Intermountain Healthcare

3. Project Definition

3.a. Project Scope

The proposed Event Publish and Subscribe Service is intended to complement existing SOA services and the SAIF Behavioural Framework (BF) for HL7. It will provide a Service Functional Model (SFM) for services, components and systems to subscribe to clinical events of interest and receive notice when new data are available. The service will support two common forms of filtering: topic-based and content-based. The interface specification will be developed according to the conventions described at http://hssp.wikispaces.com/HSSPApproach, and will be documented in a corresponding HSSP wiki.
Pre-existing conceptual and standards-development work in Event Publish and Subscribe (XMPP, OMG Data Distribution Service, ATOM) will be leveraged to help document the necessary definitions, descriptions, graphics, and artefacts that are relevant. In keeping with the approach used by other HL7 specifications, the Service Interface Specification will provide functional, semantic, and conformance profiles.
Some usage scenarios:
a) A Clinical Decision Support system for pharmacy subscribes only to those topics utilized by its rule base, including prescriptions, allergies, and diagnoses. The service does not subscribe to insurance or psychiatric topics as none of the rules in its knowledge base involve these fact types.
b) A Disease Registry service develops more descriptive logic for automatically enrolling a patient’s in a disease cohort. It unsubscribes from a number of over-general diagnoses topics, and subscribes instead to specific lab, medication, and vital sign data feeds instead.
c) An Emergency Response Coordination system publishes casualty information including clinical acuity, injury type, subspecialty services required to all area hospitals and medical centers using a guaranteed delivery mechanism. Facilities respond accordingly if their resources and capacity match a particular patient’s requirements.
d) The pharmacy personnel in a large medical center use a secure instant messaging service to communicate - the service leverages user presence to help direct questions to those senior pharmacists that are online and available.
e) A patient scheduling system might consume a consult request topic and automatically provide available time slots for a booking clerk to adjudicate.

3.b. Project Need

A generalized Event Publish & Subscribe Service is needed as a foundation for a wide variety of SOA applications, including new result feeds, content syndication, rich presence, clinical workflow systems, and any other application that requires event notifications to operate and perform efficiently. Publish and subscribe supports smaller, more loosely coupled modules, which promise to improve general manageability. In general, Pub/Sub offers event consumers the following:
· Architectural flexibility enabling event subscribers to be easily added, managed, and notified of clinical events.
· Consumer empowerment, allowing stakeholders to manage their own data requirements and subscriptions more efficiently and dynamically.
· More efficient resource utilization resulting from needing to forward messages only to interested parties.
· Enhanced performance and scalability is possible if events are processed in parallel.

3.c. Success Criteria

An Event Publish & Subscribe Service Interface Specification is successfully balloted and published.

3.d. Project Objectives / Deliverables / Target Dates

Target Date
Project Initiation / 2013 May
Service Requirements Specification / 2013 July
Initial Specification of Service Functional Model / 2013 November
Ballot for Comment / 2014 January
DSTU Ballot / 2014 May
DSTU Reconciled and Published / 2014 Sept

3.e. Project Requirements

As a crosscutting functional service, participation from several WG/Communities is required.

3.f. Project Risks

Risk Description / As a crosscutting functional service, participation from several WG/Communities is required.
Impact Description / Without participation, service generalization/effectiveness will be suboptimal.
Probability: / High / Medium / Low
/ Severity: / High / Medium / Low
Mitigation Plan / Active communication/”marketing” from CDS and SOA.

3.g. Project Dependencies

This project is intended to interface closely with the SOA/CDS modeling efforts, SAIF and standards such as XMPP XEP-0060 and OMG Data Distribution Service.

3.h. Project Document Repository Location

TBD

3.i. Backwards Compatibility

HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement
Are the items being produced by this project backward compatible? / Yes / No / Don’t Know / N/A
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement

4. Products

HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement
Non Product Project- (Educ. Marketing, Elec. Services, etc.)
/ V3 Documents - Knowledge
Arden Syntax
/ V3 Foundation – RIM
Clinical Context Object Workgroup (CCOW)
/ V3 Foundation – Vocab Domains & Value Sets
Domain Analysis Model (DAM)
/ V3 Messages - Administrative
Electronic Health Record (EHR)
/ V3 Messages - Clinical
Functional Profile
/ V3 Messages - Departmental
V2 Messages – Administrative
/ V3 Messages - Infrastructure
V2 Messages - Clinical
/ V3 Rules - GELLO
V2 Messages - Departmental
/ V3 Services – Java Services (ITS Work Group)
V2 Messages – Infrastructure
/ V3 Services – Web Services
V3 Documents – Administrative (e.g. SPL)
/ - New Product Definition -
V3 Documents – Clinical (e.g. CDA)
/ - New/Modified HL7 Policy/Procedure/Process -

5. Project Intent (check all that apply)

Create new standard
Revise current standard (see text box below)
Reaffirmation of a standard
New/Modified HL7 Policy/Procedure/Process
Withdraw an Informative Document
N/A (Project not directly related to an HL7 Standard)
/ Supplement to a current standard
Implementation Guide (IG) will be created/modified
Project is adopting/endorsing an externally developed IG
(specify external organization in Sec. 6 below)
Externally developed IG is to be Adopted
Externally developed IG is to be Endorsed
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement

5.a. Ballot Type (check all that apply)

Comment Only
Informative
DSTU to Normative
/ Normative (no DSTU)
Joint Ballot (with other SDOs or HL7 Work Groups)
N/A (project won’t go through ballot)
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement

5.b. Joint Copyright

Check this box if you will be pursuing a joint copyright. Note that when this box is checked, a Joint Copyright Letter of Agreement must be submitted to the TSC in order for the PSS to receive TSC approval.

Joint Copyrighted Material will be produced

6. Project Approval Dates

Sponsoring Group Approval Date / OO Approval Date CCYY-MM-DD
Steering Division Approval Date / SD Approval Date CCYY-MM-DD
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement
PBS Metrics Reviewed? (required for SD Approval) / Yes / No
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement
Technical Steering Committee Approval Date / TSC Approval Date CCYY-MM-DD
Joint Copyright Letter of Agreement received? (req'd for Joint Copyrighted material) / Yes / No

7. External Project Collaboration

Although no direct coordination is required, final outcome needs to be clearly communicated to other profilers basing their work on V3 messages/services.

7.a. Stakeholders / Vendors / Providers

HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement
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
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement

7.b. Synchronization With Other SDOs / Profilers

HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement
Check all SDO / Profilers which your project deliverable(s) are associated with.
ASC X12 / CHA / LOINC
AHIP / DICOM / NCPDP
ASTM / GS1 / NAACCR
BioPharma Association (SAFE) / IEEE / Object Management Group (OMG)
CEN/TC 251 / IHE / The Health Story Project
CHCF / IHTSDO / WEDI
CLSI / ISO / Other (specify below)
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement

8. Realm

HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement
Universal
/ Realm Specific
Check here if this standard balloted or was previously approved as realm specific standard
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement

9. Strategic Initiative Reference – For PMO/TSC Use Only

HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement
This section used only for Strategic Initiative Projects.
1. HL7 Recognition
2. HL7 Internal Processes
3. HL7 Implementation
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4

/ Health Level Seven®, International
2013 Project Scope Statement
HL7 Project Scope Statement v2013_template_only / 2013 Release / Page 2 of 4