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.

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

 

 

Guidance on Implementation of Standard Electronic Attachments for Health Care Transactions (ACP)

Project ID: 1398

 

 

TSC Notification Informative/STU to Normative          

Date :  01/16/18

 

Check this box when the project proceeds from Informative to Normative or STU to Normative status.  Forward to the TSC for notification, as this triggers American National Standards Institute (ANSI) Project Initiation Notification (PINS) submission.   

 

 

Investigative Project

Date : 

Check this box when the project is investigative or exploratory in nature, which allows limited project scope definition.  Sections in bold outline are mandatory for project approval of an investigative project; all other sections are optional. Sections 1-Project Name and Scope, 2-Sponsoring Group(s)/Project Team, 3a-Project Scope, 3b-Project Need, 3g-Project Objective, 3i-Project Document Repository, 6b-[Realm, if known], and 6d-[applicable Approval Dates] are required.

Investigative Project specific instructions are highlighted in yellow.

An investigative project must advance in two WGM cycles, requiring a full scope statement.  Otherwise the project will be closed.

  1.  
  1. Sponsoring Group(s) / Project Team

2.a. Primary Sponsor/Work Group

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

Attachment Work Group

2.b.  

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

Co-sponsor Work Group(s)

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

None

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

Request formal content review prior to ballot

Request periodic project updates. Specify period:  Monthly, at WGMs, etc.

Other Involvement. Specify details here:  Enter other involvement here

2.c.  

2.c. Project Team

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

Project facilitator ( 1 Mandatory )

Durwin Day, Christol Green, Craig Gabron

Other interested parties and their roles

 

Multi-disciplinary project team (recommended)

 

Modeling facilitator

 

Publishing facilitator

Christol Green

Vocabulary facilitator

 

Domain expert rep

 

Business requirement analyst

 

Conformance facilitator (for IG projects)

 

Other facilitators (SOA, etc)

 

 

 

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

This Joint ASC X12, WEDI and HL7 Informative white paper is focused on the business and operational processes of exchanging additional information (Attachments) using the HL7 standards for clinical information and the X12 transaction sets for requesting and receiving the additional information. The detailed technical requirements are not covered in this white paper as the standards development organizations have provided the technical guidance in the standards implementation documents.

 

This white paper will provide the following:

        An overview of Attachments
        Resources needed to have a successful implementation of Attachments
        A review of some of the current processes for requesting and responding to the need for additional information to help understand the challenges
        Examples of implementation approaches in the industry
        A review of Electronic Attachment Business flows for Claims, Prior Authorizations and Notification
        Business use cases and examples
        A guidance on how to embed additional information within the applicable ASC X12N transaction.

3.b.  

3.b. Project Need

Due to the upcoming Attachment Regulation, the industry needs detailed guidance and information on implementing Attachments. There are three SDO’s involved and this Informative white paper highlights the role each organization plays. This project will help ensure successful implementation and compliance.

3.c.  

3.c. Security Risks

None

 

 

Yes

 

 

No

 

 

Unknown

 

3.d.  

3.d. External Drivers

The date for the project will be determined upon the release of the final rule on Attachments. It is the goal of the project to have the project completed prior to the announcement in the Federal Register.

3.e.  

3.e. Project Objectives / Deliverables / Target Dates

 

Target Date

Enter objective/deliverable here.

All planned ballots and their target dates should be included

The example below is a "STU to Normative" path

Enter Target Date

Submit Project Scope Statement

2018 January

Obtain US Realm Approval

2018 January

Obtain DESD Approval

2018 January

Obtain ARB Approval

2018 January

Submit for Informative Ballot

2018 May

Complete Comment Reconciliation

2018 May - September

Submit Artifact Publication request

2018 October

 

 

 

 

Project End Date (all objectives have been met)

Note:  For PSS-Lite/Investigative Project, End date must be no more than two WGM cycles, e.g. project initiated at January WGM must complete investigation by September WGM.

2018 October

3.f.     

3.f.    Common Names / Keywords / Aliases

ACP - Attachment Collaboration Project

3.g.  

3.g. Lineage

None

3.h.  

3.h. Project Dependencies

Issuance of government regulation on Attachments

3.i.     

3.i.    Project Document Repository Location

AWG Documents

3.j.     

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:

If desired, enter additional information regarding Backwards Compatibility.

3.k.  

3.k. External Vocabularies

Will this project include/reference external vocabularies?

 

 

Yes

 

 

No

 

 

Unknown

 

X

N/A

 

 

 

 

 

 

 

 

 

 

 

 

If yes, please list the vocabularies:

3.l.     

  1. Products (check all that apply)

 

Arden Syntax

 

 

V2 Messages – Administrative

 

Clinical Context Object Workgroup (CCOW)

 

 

V2 Messages - Clinical

 

Domain Analysis Model (DAM)

 

 

V2 Messages - Departmental

 

Electronic Health Record (EHR) Functional Profile

 

 

V2 Messages – Infrastructure

 

FHIR Extensions

 

 

V3 Domain Information Model (DIM / DMIM)

 

FHIR Implementation Guide

 

 

V3 Documents – Administrative (e.g. SPL)

 

FHIR Profiles

 

 

V3 Documents – Clinical (e.g. CDA)

 

FHIR Resources

 

 

V3 Documents - Knowledge

X

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

 

 

V3 Foundation – RIM

 

Logical Model

 

 

V3 Foundation – Vocab Domains & Value Sets

 

New/Modified/HL7 Policy/Procedure/Process

 

 

V3 Messages - Administrative

 

New Product Definition (please define below)

 

 

V3 Messages - Clinical

 

New Product Family (please define below)

 

 

V3 Messages - Departmental

 

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

 

 

V3 Messages - Infrastructure

X

White Paper

 

 

V3 Rules - GELLO

 

 

 

 

V3 Services – Java Services (ITS Work Group)

 

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

 

 

V3 Services – Web Services (SOA)

  1.  

If you checked New Product Definition or New Product Family, please define below:

  1.  
  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;

 

Withdraw an Informative Document

 

 

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)

  1.  

If revising a current standard, indicate the following:

-         Name of the standard being revised

-         Date it was published (or request for publication, or ANSI designation date)

-         Rationale for revision

-         The relationship between the new standard and the current standard (is it designed to replace the current standard, a supplement to the current standard, etc.)

  1.  

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

 

 

 

7.b.  

If necessary, add any additional ballot information here.  If artifacts will be jointly balloted with other SDOs, list the other groups.

7.c.  

7.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?

 

X

Yes

 

 

No

 

 

 

  1. Project Logistics

6.a. External Project Collaboration

WEDI MOU on file

ASC X12 MOU on file

For projects that have some of their content already developed:

How much content for this project is already developed?

100%

Was the content externally developed (Y/N)? 

Jointly WEDI/ASC X12

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

 

 

 

 

 

 

 

 

Yes

 

X

No

 

6.b.  

6.b. Realm

 

Universal     - OR -

 

X

US Realm Specific

 

 

 

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

 

This is US realm specific. Informative paper is in support of the upcoming Attachment regulation under HIPAA.

6.c.  

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

X

N/A

 

N/A

 

Other (specify below)

 

 

 

 

X

N/A

 

 

Other:  N/A

 

 

6.d. Project Approval Dates

Affiliate Approval Date (for Affiliate Specific Projects):

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

US Realm Steering Committee Approval Date
(for US Realm Specific Projects):

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

Sponsoring Work Group Approval Date:

WG Approval Date CCYY-MM-DD

Co-Sponsor Group Approval Date

(Copy this entire row for each co-sponsor; indicate the specific cosponsor that issued approval)

Co-Sponsor Approval Date CCYY-MM-DD

FHIR Project: FHIR Management Group Approval Date:

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

Architectural Review Board Approval Date:

(required for externally developed content)

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

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

Technical Steering Committee Approval Date:

TSC Approval Date CCYY-MM-DD

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

 

 

 

 

 

 

 

 

Yes

 

No

 

N/A

6.e.