Page tree

NOTE : Please spell out all acronyms the first time the acronym occurs. 

For Reaffirmations, please refer to the FAQ within Appendix C of the PSS_with_instructions template for a list of which sections and fields should be completed.

PSS-Lite/Investigative Projects:  Sections surrounded by a BOLD OUTLINE must be completed for approval of "Investigative Projects" (a.k.a PSS-Lite).

  1. Project Name and ID

 

 

DAM coordination analysis project, aka

Allergy/Intolerance and Immunization DAM Coordination Analysis

Project ID:

Complete this section for all “Direct to Normative” ballot projects and when a project proceeds from “Informative to Normative” or “STU to Normative”. Forward PSS to the TSC (via tscpm@HL7.org ); this triggers American National Standards Institute (ANSI) Project Initiation Notification (PINS) submission.

 

 

TSC Notification:  Informative/STU to Normative 

Date: 

 

 

- or -                     Direct to Normative (no STU) (includes reaffirmations)       

 

Identify ISO, IEC or ISO/IEC standard to be adopted in text box below

 

Includes text from ISO, IEC or ISO/IEC standard: Check here if this standard includes excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption.

 

 

Yes

 

x

No

 

 

 

 

 

Select the unit of measure used in the standard; if no measurements are in the standard, select N/A

 

x

N/A

 

 

U.S.

 

 

Metric

 

 

Both

 

 

Investigative Project (aka PSS-Lite)

Date : 

 

  1. Sponsoring Group(s) / Project Team

2.a. Primary Sponsor/Work Group

Primary Sponsor/Work Group
(1 (And Only 1) Allowed)

CIC

2.b. Co-sponsor Work Group(s)

Co-sponsor Work Group(s)

(Enter co-sponsor approval dates in Section 6.d Project Approval Dates)

 

PC

Indicate the level of involvement that the co-sponsor will have for this project:

x

Request formal content review prior to ballot

 

Request periodic project updates. Specify period: 

 

 

Other Involvement. Specify details here: 

 

Co-sponsor Work Group(s)

(Enter co-sponsor approval dates in Section 6.d Project Approval Dates)

 

EHR

Indicate the level of involvement that the co-sponsor will have for this project:

X

Request formal content review prior to ballot

 

Request periodic project updates. Specify period: 

 

 

Other Involvement. Specify details here: 

 

Co-sponsor Work Group(s)

(Enter co-sponsor approval dates in Section 6.d Project Approval Dates)

 

Public Health

Indicate the level of involvement that the co-sponsor will have for this project:

x

Request formal content review prior to ballot

 

Request periodic project updates. Specify period: 

 

 

Other Involvement. Specify details here: 

 

 

 

2.c. Project Team

 

All names should have confirmed their role in the project prior to submission to the TSC.

Project facilitator ( 1 Mandatory )

Jay Lyle (jay.lyle@jpsys.com)

Other interested parties and their roles

 

Multi-disciplinary project team (recommended)

 

Modeling facilitator

Galen Mulrooney (Allergy) (gem@jpsys.com)

Steve Hufnagel (Immunization) ()

Publishing facilitator

 

Vocabulary facilitator

Rob McClure (rmcclure@mdpartners.com), Susan Matney (Susan.Matney@imail.org)

Domain expert rep

[co-chairs]

Business requirement analyst

 

Conformance facilitator (for IG projects)

 

Other facilitators (SOA, etc)

Sean Muir at SOA

Steve Hufnagel at EHR-Public Health

 

 

Implementers (2 Mandatory for STU projects)

FHIR Project Note: The implementer requirement will be handled by the “balloting” project.  Therefore work groups do not fill out the above section.  However, feel free to list implementers specific to your work group’s resources if you know of any.

1) 

2) 

  1. Project Definition

3.a. Project Scope

  • Model the Allergy DAM and the Immunization DAM in the same UML model
  • Harmonize overlap between the two DAMs in the integrated UML model to support
    • reuse of common assets (patient, organization, reaction, substance)
    • harmonization of shared assets in downstream products
    • multiple context-specific terminology bindings to disambiguate properties
    • map and gap DAMs against FHIM domains and EHR-S FM
    • possible future web publication for broad review
  • Produce a white paper summarizing findings with respect to harmonization issues and opportunities
    • We expect this to clarify the degree of gap and overlap, issues and assumptions underlying the respective prior efforts, and potential paths for supporting harmonized specifications.
    • This project is not expected to influence any specifications in the immediate term; its outcome may demonstrate that such influence is possible.

 

 

3.b. Project Need

This project will demonstrate a process and toolset that will reduce workload and enable broader reuse of assets by providing

  • a maintainable DAM in an open source repository
  • reuse of cross-DAM assets
  • consistency of assets across HL7 product families
  • terminology binding support
  • in future, implementation tooling

3.c. Security Risks

Will this project produce executable(s), for example, schemas, transforms, style sheets, executable program, etc.  If so the project must review and document security risks. Refer to the Cookbook for Security Considerations for additional guidance, including sample spreadsheets that may be used to conduct the security risk assessment .

 

 

Yes

 

 

X

No

 

 

 

Unknown

 

 

 

3.d. External Drivers

None

3.e. Project Objectives / Deliverables / Target Dates

 

Target Date

Complete review of DAM scope for both domains, including identification of overlapping content

11/1/18

Complete draft specification of DAM content; provide to co-sponsors

12/1/18

Complete DAM content review and updates

12/15/18

Ballot DAM for comment

2018 Jan Ballot

Revise DAMs based on ballot feedback

2/1/19

Project End Date (all objectives have been met)

2/28/19

3.f.    Common Names / Keywords / Aliases

 

3.g. Lineage

Allergy & Intolerance DAM V1

Immunization DAM V1

3.h. Project Dependencies

None

3.i.    HL7-Managed Project Document Repository Location

https://confluence.hl7.org/display/CIC/Coordinated+Domain+Analysis+Model+Study

3.j.    Backwards Compatibility

Are the items being produced by this project backward compatible?

 

 

Yes

 

 

No

 

 

Unknown

 

x

N/A

 

 

 

 

 

 

 

 

If you check 'Yes' please indicate the earliest prior release and/or version to which the compatibility applies:

 

For V3, are you using the current data types? 

(Refer to TSC position statement on new projects using R2B for more information on the current V3 data types)

 

 

Yes

 

 

No

 

 

Unknown

 

x

N/A

 

 

 

 

 

 

 

 

If you check 'No' please explain the reason:

 

3.k. External Vocabularies

Will this project include/reference external vocabularies?

 

x

Yes

 

 

No

 

 

Unknown

 

 

N/A

 

 

 

 

 

 

 

 

 

 

 

 

SNOMED CT, LOINC, FHIR, HL7, CVX used as example terminology bindings

 

  1. Products (check all that apply)

 

Arden Syntax

 

 

V2 Messages – Administrative

 

Clinical Information Modeling Initiative (CIMI)

 

 

V2 Messages – Clinical

 

Clinical Context Object Workgroup (CCOW)

 

 

V2 Messages – Departmental

 

Domain Analysis Model (DAM)

 

 

V2 Messages – Infrastructure

 

Electronic Health Record (EHR) Functional Profile

 

 

V3 Domain Information Model (DIM / DMIM)

 

FHIR Extensions

 

 

V3 Documents – Administrative (e.g. SPL)

 

FHIR Implementation Guide (enter FHIR product version below)

 

 

V3 Documents – Clinical (e.g. CDA)

 

FHIR Profiles (enter FHIR product version below)

 

 

V3 Documents – Knowledge

 

FHIR Resources

 

 

V3 Foundation – RIM

 

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

 

 

V3 Foundation – Vocab Domains & Value Sets

 

Logical Model

 

 

V3 Messages – Administrative

 

New/Modified/HL7 Policy/Procedure/Process

 

 

V3 Messages – Clinical

 

New Product Definition (please define below)

 

 

V3 Messages – Departmental

 

New Product Family (please define below)

 

 

V3 Messages – Infrastructure

 

Non Product Project - (Educ. Marketing, Elec. Services, etc.)

 

 

V3 Rules – GELLO

X

White Paper

 

 

V3 Services – Java Services (ITS Work Group)

 

Creating/Using a tool not listed in the HL7 Tool Inventory

 

 

V3 Services – Web Services (SOA)

 

FHIR STU4 Exemplar

  1. Project Intent (check all that apply)

 

Create new standard

 

 

Supplement to a current standard

 

Revise current standard (see text box below)

 

 

Implementation Guide (IG) will be created/modified

 

Reaffirmation of a standard

 

 

Project is adopting/endorsing an externally developed IG:

 

New/Modified HL7 Policy/Procedure/Process

 

 

Specify external organization in Sec. 6 below;

 

 

 

 

Externally developed IG is to be (select one):

X

White Paper (select one):

 

 

Adopted  - OR -

 

Endorsed

 

X

Balloted Informative OR

 

Non-balloted WG White Paper

 

 

N/A  (Project not directly related to an HL7 Standard)

 

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

 

Comment (aka Comment-Only)

 

 

Joint Ballot (with other SDOs)

X

Informative

 

 

N/A  (project won’t go through ballot)

 

STU to Normative     - OR -

 

Normative (no STU)

 

 

 

 

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?

 

 

Yes

 

X

No

 

 

  1. Project Logistics

6.a. External Project Collaboration

FHIM team will provide infrastructure and skilled resources

For projects that have some of their content already developed:

How much content for this project is already developed?

95%

Was the content externally developed (Y/N)? 

No

Is this a hosted (externally funded) project? 
(not asking for amount just if funded)

 

 

 

 

 

 

 

x

Yes

 

 

No

6.b. Realm

 

Universal     - OR -

 

x

Realm Specific

 

 

 

Check here if this standard balloted or was previously approved as realm specific standard

 

US Realm, due to limited project staffing rather than intended conceptual scope

6.c. Stakeholders / Vendors / Providers

This section must be completed for projects containing items expected to be ANSI approved, as it is an ANSI requirement for all ballots

 

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

X

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

 

 

 

 

6.d. Project Approval Dates

Approvals are by simple majority vote of the approving body

Sponsoring Work Group Approval Date:

CIC Approval Date 2018-10-02

Administrative review – in parallel with Work Group Approval

Co-Sponsor Group Approval Date

 

PC Approval Date 2018-10-01

PHER Approval Date 2018-10-01

EHR Approval Date 2018-10-01

Family Management Group Approval Date(s)

CIMI Projects: CIMI Management Group

CIMI MG Approval Date CCYY-MM-DD
or “N/A”

CDA Projects: CDA Management Group

CDA MG Approval Date CCYY-MM-DD
or “N/A”

FHIR Projects: FHIR Management Group

FMG Approval Date CCYY-MM-DD
or “N/A”

V2/Publishing Projects: V2 Management Group

V2 MG Approval Date CCYY-MM-DD
or “N/A”

US Realm Projects: US Realm Steering Committee Approval
(Email WG approved PSS to: tscpm@HL7.org )

USRSC Approval Date  2018-11-17

Affiliate Specific Projects: Affiliate Approval Date

Affiliate Approval Date CCYY-MM-DD or indicate “N/A”

Submit PSS to Steering Division after all of the above approvals are received

Steering Division (of Primary Sponsor WG) Approval Date:

SD Approval Date CCYY-MM-DD

Last PBS Metrics Score :

 

Green

 

Yellow

 

Red

PBS Metrics Reviewed ? (required for SD Approval if not green)

 

Yes

 

No

ARB and SGB approval may be in parallel

Architectural Review Board Approval Date:

(required for externally developed content)

ARB Approval Date CCYY-MM-DD
or “N/A”

If applicable, TSC has received a Joint Copyright/Distribution Agreement (containing the verbiage outlined within the SOU),
signed by both parties.

 

 

Yes

 

No

 

N/A

Technical Steering Committee Approval Date:
(Email SD WG approved PSS to: tscpm@HL7.org )

TSC Approval Date CCYY-MM-DD