Page tree

HL7 Project Scope Statement SOA Cross Paradigm Model Transformation Service_Final.docx

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

 

 

HL7 Cross Paradigm Model Transformation Service

Project ID: 1420

 

 

TSC Notification:  Informative/STU to Normative 

Date: 

 

 

- or -                     Direct to Normative (no STU)      

 

 

 

 

Investigative Project

Date : 

 

  1. Sponsoring Group(s) / Project Team

2.a. Primary Sponsor/Work Group

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

SOA Work Group

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

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

x

Request periodic project updates. Specify period: 

Working Group meetings

 

Other Involvement. Specify details here: 

 

 

Co-sponsor Work Group(s)

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

 

ITS

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

x

Request formal content review prior to ballot

x

Request periodic project updates. Specify period: 

Working Group meetings

x

Other Involvement. Specify details here:  Contribute examples for cross-platform use case and update at least once per working group cycle.

 

 

Co-sponsor Work Group(s)

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

 

Security

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

x

Request formal content review prior to ballot

x

Request periodic project updates. Specify period: 

Working Group Meetings

 

Other Involvement. Specify details here:  Contribute examples for cross-platform use case and update at least once per working group cycle.

 

 

Co-sponsor Work Group(s)

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

 

CIMI, CBCP, O+O

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

 

Request formal content review prior to ballot

X

Request periodic project updates. Specify period: At each working group meeting

 

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 )

Ken Lord, Sean Muir

Other interested parties and their roles

Pharmacy WG and Patient Care WG as relevant content reviewers, Office of the National Coordinator for Health Information Technology (ONC), US Substance Abuse and Mental Health Services Agency (SAMHSA), The US Department of Veterans Administration, Healthcare Services Platform Consortium (HSPC), Object Management Group (OMG), Jean Duteau and ONC Project (Jean’s team and the Cross Paradigm team have 1) agreed the projects are not competitive and 2) have agreed there is value in collaborating and have had several meetings and will continue to do so. Telstra Health Australia as reviewer and implementer.

 

Multi-disciplinary project team (recommended)

 

Modeling facilitator

Sean Muir

Publishing facilitator

 

Vocabulary facilitator

Heather Grain  

Domain expert rep

Kathleen Conner

Business requirement analyst

 

Conformance facilitator (for IG projects)

 

Other facilitators (SOA, etc)

Stefano Lotti(SOA), Vincent McCauley (SOA)

 

 

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)  MDIX, Inc.

2) Telstra Health

  1. Project Definition

3.a. Project Scope

This project will create a functional specification for transformation services with exemplary mappings using storyboards developed by the SOA Working Group, the interested parties of the Project, and co-sponsor WGs of this project. The project will create story boards that use aspects of 1) the current versions of HL7 Standards of V2, C-CDA, and FHIR, and 2) new information models such as CIMI and realm specific examples such as the FHIM. Artifacts for the Storyboards will be produced at a logical level to ensure traceability (iso-semantic relationships) between data elements as well as identify semantic gaps.  The project will use existing open source software.

 

The project addresses a major requirement of the HSSP Transformation Service. The scope of the project is limited to the exchange of data between a source and a target where the source and target include different HL7 Standards used to define or exchange information. The project will identify what semantic concepts can be exchanged accurately, where there are potential issues, and identify what cannot be exchanged.   The project scope is limited to an informative specification as SOA group does not have the responsibility to resolve any issues in the underlying standards. The project will provide input to relevant content working groups who can decide if they want or need to address such issues.  The project will not attempt to harmonize standards.

 

The project will collaborate with other HL7 Projects, particularly in the area of testing use cases and storyboards they have developed. As an example, to enable and test standard transforms across these product lines, the project will specify the syntactic   rules and relationships for assigning   security labels to HL7 v2, CDA, or FHIR content . This work will be based on the HL7 Privacy and Security Healthcare Classification System (HCS). Another component of this particular use case will be to provide recommendations on harmonizing a repeatable approach for cross-paradigm interoperability based on previous work efforts of the SOA WG and the CBCP WG.

3.b. Project Need

Since the publication of the previous Cross Paradigm Immunization Work, the business needs and the complexity for interoperability between diverse HL7 standards has increased. Examples from members of the SOA WG, co-sponsors, and interested parties attests to the need to expand the scope.

 

Examples of the need driven by business issues are CMS Accredited Care Organizations activities, emerging needs patient centric care plans and care coordination across different healthcare organizations required by the Veterans Administration, and the realization that the different HL7 formats, which have been implemented with significant investment, will need to be semantically interoperable.

 

 

The previous Cross Paradigm Interoperability work demonstrated the feasibility, agility, and value of a Model Driven Architecture (MDA) approach using an open, standard Platform Independent Model (PIM). This approach complements the HL7 Service Aware Information Framework (SAIF) for developing both logical and computable interoperability artifacts.

 

 

 

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

Patient-centric Care Plans, Care Coordination across healthcare organizations, Accountable Care Organization

3.e. Project Objectives / Deliverables / Target Dates

 

Target Date

1)     Publish service functional specification and artifacts based on the storyboards that document traceability and gap analysis.

2)     When issues and gaps are identified, they will be provided to the relevant content working group.

Enter Target Date

Participation at Baltimore Connectathon using FHIR Structured Definition and FHIR Testing.

2018 September

Participation in Sponsor and Co-Sponsor Working Groups to review use cases

2018 September WGM

Completion of FHIR, CCDA, and FHIM mappings and testing

2019 January

 

 

Completion of CIMI Use Case

2019 January

Completion of HL7 V2 and CIMI mappings and testing

2019 January

Completion of CBCP Use Case

2019 January

Review Use Case work with Sponsor and Co-Sponsor Working Groups

2019 January WGM

Notice of Intent to Ballot

2019 end of January

Submit for informational ballot (final content due 3/24/19)

2019 mid-March

Informational Ballot

2019 May

Complete Reconciliation

2019 July

Apply changes from ballot

2019 August

Submit publication request

2019 September

Project End Date (all objectives have been met)

 

2020 January

 

 

3.f.    Common Names / Keywords / Aliases

Cross Paradigm Transformation Service

3.g. Lineage

HL7 SOA Cross Paradigm Interoperability Guide for Immunizations

3.h. Project Dependencies

 

3.i.    HL7-Managed Project Document Repository Location

Supporting project documents, deliverables, ballot reconciliation work and other project information will be kept at the SOA Confluence page: https://confluence.hl7.org/display/SOA

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

 

 

 

 

 

 

 

 

 

 

 

 

If yes, please list the vocabularies:

SNOMED-CT, RXNORM, LOINC, HL7 Value sets, and others as required based on Storyboards / Use Cases.  Project will leverage SOLOR implementation.

  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

 

White Paper

 

 

V3 Services – Java Services (ITS Work Group)

 

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

 

x

V3 Services – Web Services (SOA)

 

 

  1. Project Intent (check all that apply)

x

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

 

White Paper (select one):

 

 

Adopted  - OR -

 

Endorsed

 

 

Balloted Informative OR

 

Non-balloted WG White Paper

 

 

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

This project will be informative for other working groups.

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

 

For projects that have some of their content already developed:

How much content for this project is already developed?

10%

Was the content externally developed (Y/N)? 

NO

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

 

 

 

 

 

 

 

 

Yes

 

x

No

6.b. Realm

x

Universal     - OR -

 

 

Realm Specific The US realm, FHIR US Core Profiles, and VSAC/SOLOR are important elements that will be considered

 

 

 

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

 

 

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

x

Clinical and Public Health Laboratories

 

Immunization Registries

x

EHR, PHR

x

Emergency Services

 

Quality Reporting Agencies

 

Equipment

 

Local and State Departments of Health

 

Regulatory Agency

 

Health Care IT

 

Medical Imaging Service

 

Standards Development Organizations (SDOs)

x

Clinical Decision Support Systems

x

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

 

Payors

x

Lab

 

Other (specify in text box below)

 

Other (specify in text box below)

x

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:

10/2/2018

Administrative review – in parallel with Work Group Approval

Co-Sponsor Group Approval Date

 

CIMI 4/5/2018, CBCP 7/31/2018, Security 8/14/2018, ITS 10/2/2018, Public Health 10/3/2018, O+O 10/4/2018

 

Family Management Group Approval Date(s)

CIMI Projects: CIMI Management Group

CIMI 4/5/2018

 

CDA Projects: CDA Management Group

 

FHIR Projects: FHIR Management Group

 

V2/Publishing Projects: V2 Management Group

 

US Realm Projects: US Realm Steering Committee Approval)

 

Affiliate Specific Projects: Affiliate Approval Date

 

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

 

ISD approval: 11/6/2018

Last PBS Metrics Score :

 

x

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)

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

X

N/A

Technical Steering Committee Approval Date: