08.01.2014 Views

130405 0242 Open Issue Tracker - California Health Benefit Exchange

130405 0242 Open Issue Tracker - California Health Benefit Exchange

130405 0242 Open Issue Tracker - California Health Benefit Exchange

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13158<br />

Please let me know if another meeting is going to be scheduled for the<br />

benefit and rate guide. Thank you<br />

13027 6. When does the exchange intend to announce specific dates for when file layouts will<br />

be finalized and companion guides available?<br />

Will Covered CA operate in real time or are they sending daily batch file changes in<br />

13174 834 enrollment? What is the frequency? If a daily transaction, what is the time it will be<br />

sent?<br />

13287 834<br />

13283<br />

13157<br />

13033<br />

13025<br />

You are sending us an 834 monthly, are we sending you back an 834 or are we<br />

following up via phone?<br />

The abortion rider must be billed separately, how is this information going to be<br />

transferred? Which data field will be used on the 834?<br />

What will be the procedure to make an enrollment change that creates new effective<br />

dated rate computation?<br />

Do embedded dental and vision providers need to be certified by the <strong>Exchange</strong> to be<br />

included in the EHB of a full service QHP?<br />

4 Our understanding is that the exchange will pay agent/broker commissions in the<br />

SHOP. Are Broker Commissions only applicable for SHOP? Please clarify.<br />

3-Apr-13<br />

The companion guides are posted to the bidders library and have been emailed to all technical<br />

call participants for whom I have contact information as part of the meeting materials when the<br />

topic of the meeting is that particular guide book.<br />

closed<br />

closed<br />

834 transactions will be sent daily. Time of day is not yet determined. closed<br />

834 will be transmitted daily - reconciliation will be done monthly. closed<br />

A rider is not a QHP.<br />

All effectuation date changes will be initiated in Covered CA (CC) - CC will have rules for any rate<br />

changes.<br />

All questions regarding solicitations need to be communicated as outlined in the solicitation<br />

process.<br />

ANSWER - Covered <strong>California</strong> will pay agents, general agents and secondary agents in the<br />

SHOP market only for those agents who are contracted to participate in the SHOP market. This<br />

SHOP Agent contract will allow these agents to interact with all SHOP QHP <strong>Issue</strong>rs and all SHOP<br />

Employers, unilaterally standardizing agent commissions and performance structure.<br />

13036 SERFF Are SHOP brokers included in the SERFF template/module? Broker information is transmitted in the 834 transaction files. closed<br />

13093<br />

13032<br />

834<br />

Please clarify the broker information that will be sent in the 834 and the report you will<br />

send with the applications. Also clarify how non-paid sister entities will be reported.<br />

How will CC identify PCPs through this provider data file? Could they simply add a<br />

data element of PCP – 1 char – Y or N?<br />

13030 Is the HIX file sent in by Athena correct? Please validate<br />

business process question not 834 question. On 834 broker info will be sent (1000cn1 and<br />

1000act)<br />

CalHEERS doesn‟t need identification of PCPS for any enrollment. However, a PCP is field is<br />

provided in the Provider Directory field.<br />

corrected HIX file sent back in reply with corrections highlighted in yellow (NOTE FOR<br />

CONTRACTORS - A HIX file is being prepared for distribution to the group and should be<br />

available week of 8 April)<br />

13024<br />

3.B. How will that information be sent/received between the exchange and the<br />

carrier?<br />

Covered CA is planning on sending an agent identifier on the 834 that we send to the Carrier. closed<br />

In reading the draft Companion Guide, on page 12 it mentions that the enrollee‟s SSN<br />

is transmitted in the NM1 segment on the initial enrollment transactions, but is not Covered <strong>California</strong> (CC) will follow CMS guideline and only send SSN on the initial. CC uses the<br />

13028<br />

included in maintenance transactions between the FFE and <strong>Issue</strong>r. Is this true? Since <strong>Exchange</strong> Assigned Member ID and <strong>Issue</strong>r Assigned Member IDs (both would be sent) in all closed<br />

the SSN is the main identifier for enrollees, I would hope to receive the SSN on all other transactions (updates, disenrollments).<br />

transactions for the member.<br />

13023<br />

3.A. Our understanding is that carriers are to pay any agent/broker commissions in<br />

the individual market.<br />

Covered <strong>California</strong> will not pay agents or general agents in the Individual market.<br />

closed<br />

13192 test strategy Will there be another meeting to discuss the Testing Plan and <strong>Benefit</strong> Data Currently scheduled for 11 April - Go-To meeting info will be sent out 5 April closed<br />

13225 provider dir<br />

13106<br />

13040<br />

834<br />

834<br />

Provider question: I know you have indicated a quarterly batch file for provider<br />

directory. If we send files more often, will you update the information more often? If<br />

not, are you willing to consider going back to the monthly frequency initially discussed?<br />

8.6. CHANGE IN CIRCUMSTANCE – SHOP ONLY - Can you explain what this<br />

means?<br />

On the call yesterday, there was one person who mentioned that a group file would be<br />

sent with all the employer data we need for SHOP members. Can you confirm this?<br />

I‟ve heard about this group file on the calls that CMS was having for the FFE 834 but<br />

not in the CC arena<br />

Currently this will happen quarterly. Consideration for update frequency can be discussed in the<br />

future.<br />

following CMS companion guide - OLIVER TO POST CMS COMPANION GUIDE TO BIDDERS<br />

LIBRARY AND SEND OUT TO ALL TECH CONTACTS<br />

group setup - there will be another companion guide for group setup. The Group Setup Guide is<br />

due to be posted to the bidder's library 23 April with a technical call for that date on 30 April.<br />

closed<br />

closed<br />

closed<br />

closed<br />

closed<br />

closed<br />

closed<br />

closed<br />

closed<br />

closed<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 1 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13190 test strategy<br />

The presenter has discussed the testing of the 834/820 transactions. What about other<br />

transactions such as group setup and provider files?<br />

group setup - there will be another companion guide for group setup. The Group Setup Guide is<br />

due to be posted to the bidder's library 23 April with a technical call for that date on 30 April.<br />

834 and 820 data will be needed for testing 3 June.<br />

Provider files will be needed by first stage testers by 15 April. Provider files by 2nd stage testers<br />

will be required by 3 June.<br />

closed<br />

13200<br />

We were told at one point the Group Setup file would be sent separately and in<br />

advance. Are you now saying groups will be in the 834.<br />

group setup - there will be another companion guide for group setup. The Group Setup Guide is<br />

due to be posted to the bidder's library 23 April with a technical call for that topic on 30 April.<br />

834 and 820 data will be needed for testing 3 June<br />

13202 please email links to bidder‟s library http://www.healthexchange.ca.gov/Solicitations/Pages/QHPSolicitation.aspx closed<br />

13227 URL please post the bidder library URL http://www.healthexchange.ca.gov/Solicitations/Pages/QHPSolicitation.aspx closed<br />

13203<br />

1. When will the SERFF Plan Management Module for <strong>California</strong> be available? It is<br />

available now.<br />

http://www.serff.com/#<br />

closed<br />

13196 SERFF<br />

please post instructions on how to get onto SERFF?<br />

http://www.serff.com/#<br />

http://www.serff.com/plan_management_data_templates.htm<br />

SERFF training is available on this website<br />

closed<br />

13088<br />

13097<br />

834<br />

834<br />

13047 834<br />

If a dependent is added will this be considered a change in coverage? Will this require<br />

a termination & add as described in section 8.5 even?<br />

if adding it is not a termination and add it is a trans to add only<br />

Could you please clarify rules you use to determine the subscriber in a family - (Oldest In a house hold, the person who is filling out the application is a person getting insurance they will<br />

family member is "made" subscriber)?<br />

be subscriber otherwise oldest is default<br />

The companion guide states that Covered <strong>California</strong> will send a monthly 834 and the<br />

In answer to her question – the reporting of errors on the 834 is a manual process<br />

QHP will use that to reconcile in their system. It then states that the QHP will report an<br />

discrepancies to Covered <strong>California</strong>. However, it doesn‟t state how the QHP is<br />

I would double check with the technical folks as I do believe that there are some established 834<br />

reporting the discrepancies? Are we sending an additional 834 back to Covered<br />

reportable transmission errors that exist in this process as well.<br />

<strong>California</strong> or is it a manual process?<br />

13305 834 1. Please confirm that a member will always have a unique CC assigned member ID. In the individual market all members are assigned a unique member ID closed<br />

13301<br />

2. Will a member's APTC be determined on a monthly basis or during initial enrollment<br />

initial and redetermination only.<br />

and any redetermination.<br />

closed<br />

13102<br />

On enrollment effectuation - should the Maintenance Type Code for 2000 INS03 be<br />

834 021? looking for CMS to provide guideline<br />

closed<br />

13095 834 Can you please add the DMG segment and elements used to the companion guide? newer version has that in it closed<br />

13199 Will all carriers be invited to the meetings with the testers? no closed<br />

13193 provider dir<br />

Has CALHEERS decided to add the PCP selection if the member in the 834 feed to the No PCP data will be sent. The system is not designed to allow PCP selection during the<br />

carrier?Load? We are interesting in getting the timing, what to submit and how. enrollment process.<br />

closed<br />

closed<br />

closed<br />

closed<br />

closed<br />

13105<br />

834<br />

13317 SERFF<br />

13100<br />

834<br />

13045 SERFF<br />

In 8.4 SHOP Market Re-enrollment - Will reinstatements never occur?<br />

Reinstatements with or without a lapse, members canceled in error, etc? Would a new<br />

QHP member ID need to be generated? If so will the exchange be able to handle this? no reinstatements in SHOP<br />

It is my understanding there are fees associated with serff submissions, will we need to Rates are required to be submitted to regulators via SERFF. More information is available on the<br />

pay fees for the test data submission?<br />

SERFF website. The SERFF link is: http://www.serff.com/#<br />

On enrollment effectuation - Will the QTY totals represent what was sent on inbound or<br />

actual totals computed from the membership being sent on the outbound?<br />

reflect on what we sent to them (inbound)<br />

templates are not final until 29 March - can we have a later date for the test data in<br />

see # 13044<br />

SERFF template format to be due and if so what date?<br />

closed<br />

closed<br />

closed<br />

closed<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 2 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13042 SERFF<br />

What is the deadline for uploading the templates to SERFF?<br />

1. Administrative template<br />

2. Plan rates and benefit template<br />

3. Service area template<br />

4. Network template<br />

13245 test strategy<br />

templates previously communicated?<br />

See # 13044 for test strategy. All test data will be provided to CALHEERS via excel files. DO<br />

NOT UPLOAD TEST DATA TO THE SERFF WEBSITE.<br />

13197 please update the posted plan tech sched and the test strategy see # 131195 answer closed<br />

13194<br />

Connectivity date Test Plans and Test cases availability... Testing will start when for<br />

test strategy<br />

the 2 Carriers... Other Carriers will start when?<br />

see # 13195<br />

closed<br />

Based on the 834 Companion Guides, the <strong>Exchange</strong>s will be sending a member's<br />

responsible SR amount in dollars instead of a percentage. It seems it will be difficult, if<br />

13312 834<br />

not impossible, to determine copay amounts from a specific dollar amount. Since CSR<br />

see answer to # 130046<br />

applies to copays, we need to know how the <strong>Exchange</strong>s expect carriers to determine<br />

closed<br />

the different copay amounts from he information provided in the 834. Is it possible for<br />

the <strong>Exchange</strong>s to calculate CSR and send percentage instead?<br />

Clarification on the 4/15 test data date: for those bidders that are selected for the first<br />

round of testing, are you expecting anything in addition to the Plan/Network/Rate serff<br />

closed<br />

13038 SERFF<br />

When we try to open the hyperlink or attach the url to the internet browser in the<br />

DRAFT Plan <strong>Benefit</strong> and Rate Implementation Guide we receive an error message (the<br />

file does not exist).We are trying to view these templates and I can‟t seem to locate<br />

them through the SERFF website either, can you assist?<br />

see test strategy already answered above. All test data templates will be listed in the ITD (this list<br />

will be filled in here 8 April)<br />

SERFF has updated their links - we are updating the guide books with the current links now.<br />

They will be resent to all bidders. With each updated version of the guide books the links will be<br />

tested to ensure they work at the time the guide is posted.<br />

Testing with issuers will follow a two stage process.<br />

The first stage testing will include three issuers and will focus on confirming that the CalHEERS<br />

application correctly generates the outbound transactions and correctly processes the issuer‟s<br />

response. CalHEERS is scheduled to begin the coordination and planning activities with the<br />

three issuers in April. Test cases will be supplied to all issuers during the planning process.<br />

Connectivity testing is expected to occur mid to late May.<br />

• Only the 3 first stage test issuers need to provide representative test data on 15 April. No<br />

other bidders need to provide test data in April or May.<br />

CLOSED<br />

closed<br />

13044 test strategy Is the test data still due on 1 April? (which is a holiday)<br />

• First stage testing kick off meetings will happen with each of the 3 chosen initial test issuers<br />

as soon as can be scheduled. Attendance will be technical personnel as identified by each side.<br />

Each meeting will be one on one between CalHEERS and issuers.<br />

• Transactional testing between the three issuers and CalHEERS is scheduled to begin mid-<br />

May and run through July.<br />

• Testing in June and July will utilize test data submitted by the first stage testing issuers on<br />

April 15 as well as the test data required from the rest of the issuers on June 3rd.<br />

The second stage of testing will include the remaining issuers and will focus on certifying that<br />

each issuer can process inbound transactions and generate appropriate responses. A<br />

CalHEERS testing resource will work with an issuer to identify an individual testing window. Test<br />

cases utilized during the first phase will be repurposed for certification testing. Certification<br />

testing is expected to begin on July 22 and continue through September 6.<br />

closed<br />

13195 test strategy please post the test strategy see answer to # 13044 closed<br />

13204 test strategy<br />

2. For the April 1 st Plan Management Data test, where is this data submitted? The<br />

chosen first stage test parties will be identified and contacted with all required<br />

information and dates.<br />

see answer to # 13044<br />

closed<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 3 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13261 test strategy<br />

13263 test strategy<br />

13313 834<br />

13314 test strategy<br />

We do not have SERFF access yet, though we started the process weeks ago – we<br />

have been calling SERFF and they have not responded, except to say they would get<br />

back to us on April 3d. This will hinder us getting the TESTING templates to you via<br />

SERFF by April 1. We need an extension to the April 1 deadline to submit test data for see answer to # 13044<br />

this reason. Alternatively, we are planning to load the plan, benefit and rate test data in<br />

the templates and then email them directly to you by April 1. Please let us know ASAP<br />

whether or not this will work for you.<br />

I was a bit confused on the call yesterday. If I am correct, there will be test files given to<br />

CalHEERS on April 15th by 2-4 issuers using mock-up data. And the larger group will<br />

submit files sometime in July.<br />

Does this mean that the Provider Directory is no longer due to the <strong>Exchange</strong> June 1st?<br />

Do the benefit designs in each region have any relationship to our “service area”<br />

template (is service area based solely on the areas in which the plan is licensed?)<br />

I just want to verify that I am understanding the test strategy. In yesterday's meeting,<br />

the testing for the 834 & 820 transactions will be with 2 carriers.<br />

Then there was some discussion about the test data for the plan load, etc. which was<br />

originally due 4/1. Is this phase also going to be with the 2 carriers chosen? Is the 4/1<br />

due date for plan, benefit, and provider pushed out? Or should we be panicking to hit<br />

that 4/1 date? It sounded like we have a reprieve. Please advise. Thanks.<br />

see answer to # 13044<br />

see answer to # 13044<br />

see answer to # 13044<br />

closed<br />

closed<br />

closed<br />

closed<br />

13139 834<br />

CMS published a document with 834 scenarios (see attach) can we get sample<br />

transactions for all these scenarios?<br />

The 834 guide is posted in the bidder's library. CMS is due to release some updated information<br />

that will require us to update our 834 guide. The CMS information is due out any day now, so we<br />

want to have the follow-on 834 call after they give us their update and we have updated our guide<br />

books to reflect that information. We are planning on the next 834 call to happen on 25 April.<br />

closed<br />

13201 please post the material from the 834 call<br />

13046 834<br />

Based on the 834 Guide CC will be sending a member's responsible CSR amount in $<br />

instead of a %. It seems difficult if not impossible to determine copay amounts from a<br />

specific dollar amount.<br />

Since CSR applies to copays, issuers need to know how CC expects issuers to<br />

determine the different copay amounts from the information on the 834.<br />

Is it possible for CC to calculate CSR and send a percentage instead?<br />

The 834 guide is posted in the bidder's library. CMS is due to release some updated information<br />

that will require us to update our 834 guide. The CMS information is due out any day now, so we<br />

want to have the follow-on 834 call after they give us their update and we have updated our guide<br />

books to reflect that information. We are planning on the next 834 call to happen on 25 April.<br />

The CSR amount represents the CMS approved PMPM ESTIMATE to be advanced to<br />

contractors. The contractors are responsible for submitting to CMS their ESTIMATE PMPM for<br />

approval.<br />

13282 What are premium paid dates, the date a premium was paid or paid through? The date the premium is paid. closed<br />

The <strong>Exchange</strong> (COVERED CALIFORNIA) will be the point of contact to update /change<br />

2 Can an enrollee change e.g. their demographic data, add dependents etc. by<br />

13022<br />

members‟ information. As a result the info will then flow to the carriers and both systems will stay closed<br />

contacting their plans, or do they have to contact the <strong>Exchange</strong> directly?<br />

true.<br />

13021 1 For individual members, what changes will/can be made by the carriers?<br />

13304 SERFF<br />

13034<br />

Will links/templates in the Draft Plan <strong>Benefit</strong> and Rate Implementation Guide be<br />

updated to include the most recent CMS 3/27/13 template updates for the three QHP<br />

templates – Prescription Drug Template, Rate Tables Template, and Plan & <strong>Benefit</strong>s<br />

Add-In Template to fix defects found during testing?<br />

The <strong>Exchange</strong> (COVERED CALIFORNIA) will update members‟ information and as a result it will<br />

get uploaded to carriers. This way both systems stay true.<br />

The links and the screen views to the templates in the Guides will be tested and updated with<br />

each guide update. Changes to the templates themselves is not in Covered CA or CALHEERS<br />

control but any errors found during testing will be relayed to CMS.<br />

Yesterday in the tech meeting, there was mention at the very end of the meeting that<br />

the embedded pediatric dental and vision providers will need to be included in the<br />

The provider directory is per issuer. Any Provider for which the plan includes within their network<br />

Provider Directory. Can they verify that this is correct and that it will not be a separate<br />

should be included.<br />

directory? Do any acupuncture providers also need to be included? We are required to<br />

cover medically necessary acupuncture per the benchmark plan.<br />

closed<br />

closed<br />

closed<br />

closed<br />

closed<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 4 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13041 provider dir<br />

13205 provider dir<br />

Will the <strong>Exchange</strong> use a standard directory format, or will there be the flexibility to<br />

accommodate the PPG configuration. contractor HMO directories list the PPG and<br />

hospitals and PCPs affiliated with the PPGs<br />

The provider directory data is due to the <strong>Exchange</strong> on 06/01/13. Will contractor have<br />

an opportunity to update the data before the Fall <strong>Open</strong> Enrollment? Will health plans<br />

be able to submit directory files on a monthly basis?<br />

3. On the Networks template, what is the URL that is being requested? this should<br />

be your organization's provider network URL.<br />

The Provider directory is submitted for testing (and later upload to CALHEERS) in the SERFF<br />

format. The Draft Provider Directory Guide is posted in the bidder's library. An updated version<br />

will be posted soon, but the edits to the update do not have any changes to content.<br />

Live Provider Directory information uploaded to CALHEERS will be updated quarterly.<br />

The URL that links to the contractors provider search<br />

closed<br />

closed<br />

13090<br />

they were released in oct 2012 so they need to update and as soon as they do we will distribute.<br />

CMS is due to release some updated information that will require us to update our 834 guide.<br />

The CMS information is due out any day now, so we want to have the follow-on 834 call after they<br />

closed<br />

834<br />

CMS published a document with 834 scenarios (see attach) can we get sample<br />

transactions for all these scenarios?<br />

give us their update and we have updated our guide books to reflect that information. We are<br />

planning on the next 834 call to happen on 25 April.<br />

While the NPI is a required element, we do not have it for all providers: providers who<br />

13253<br />

do not bill Medicare are not motivated to provide it. Therefore it will be blank for some This field cannot be blank. The data will error if missing NPI<br />

closed<br />

providers. How do we handle this currently required field given this reality?<br />

13311 provider dir<br />

Under what circumstances will “FFS Provider” (#50) and “FFS Provider County” (#51)<br />

be required to be completed?<br />

this is for Medi-Cal only<br />

closed<br />

13243 provider dir What is a network tier ID?<br />

This is only applicable if you are offering 2-tier network plans. If you do not have 2-tier networks<br />

then this field is not applicable to you.<br />

closed<br />

13236 provider dir We have a network ID but not the Tier Tier is not required closed<br />

13259<br />

Can we get the provider taxonomy list you plan on using (or let us know when it will be Updated taxonomy will be available soon(and shared as soon as available) - but for now use the<br />

available)?<br />

taxonomy codes you normally use.<br />

closed<br />

13039 SERFF<br />

The feds have been posting updated templates<br />

(http://www.serff.com/draft_plan_management_data_templates.htm)<br />

and conducting trainings (attached) Do you have any idea whether CA <strong>Exchange</strong> will<br />

use the federal plan management templates or will be using their own? In other words,<br />

is Covered <strong>California</strong> is expecting plans to participate in these trainings and use these<br />

templates designed for the Federal <strong>Exchange</strong> and State Partnership <strong>Exchange</strong>s?<br />

We are using these templates as well as the SERFF Plan Management module.<br />

PLEASE attend the training you find pertinent in this flyer. It will help you as we move forward<br />

with our calls and discussions.<br />

13228 provider dir when will the provider directory be updated?<br />

We will post an updated provider directory, however, current edits do not include changes to<br />

current content.<br />

closed<br />

13103<br />

On enrollment effectuation - in 2700 do we need to send back whatever is sent on<br />

834 inbound? Flow diagram needed.<br />

what was sent as inbound needs to be sent back.<br />

closed<br />

13084<br />

Need confirmation that multiple Groups/Sponsors will be represented in a single 834.<br />

834 Can the 834s be grouped by Sponsor? (SHOP only)<br />

whatever info has changed in system GetInsured (GI) will create 1 for each carrier and individual<br />

closed<br />

13043 SERFF Is the test data supposed to be provided in SERFF template form? yes closed<br />

13098 834 Will the state require TA1 on files that are good? yes closed<br />

13175 Will contractor have view access into Covered CA's website for pending enrollments? Yes closed<br />

13176<br />

Is the <strong>Exchange</strong> the system of truth for all changes? What about items that impact<br />

eligibility vs. items that do not have an eligibility impact?<br />

Yes - Covered CA(CC)/<strong>Exchange</strong> is the system of record<br />

closed<br />

13165<br />

If a person re-ages during the plan year, will a rate change need to be held off until the Yes - rate base - Rate is based on age @ enrollment. It does not change until next enrollment<br />

next plan year or is a change allowable mid-plan year?<br />

year.<br />

closed<br />

13031<br />

Please confirm that the provider data submitted by a full service QHP should include Yes for the purposes of loading into CalHEERS the single directory file as provided in Provider<br />

the embedded behavioral health, dental and vision providers.<br />

Directory Guide will include behavioral health, dental and vision providers.<br />

closed<br />

13198 Is it possible for the carriers to obtain copies of the test scenarios? yes they will be shared with the full group of technical call participants closed<br />

closed<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 5 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13026<br />

4 March - Right now all transactiosn are expected to be processed within 24 hours. However,<br />

5. When will SLAs be shared with carriers for transaction TATs etc.<br />

not sure what is meant by “time to complete an enrollment”. If this is in relation to sending the<br />

CLARIFICATION 21 Feb - When will the service level agreements be published<br />

834 transaction, then the 24 hour timeframe is expected. If it means the time to send a health<br />

specifying the turnaround times for all transactions. For example, what is the maximum<br />

plan card and packet, then (Enrollment and Eligibility) Thien will need to provide that answer.<br />

time an enrollment transaction must be acknowledged? And what is the maximum time<br />

to complete an enrollment.<br />

open<br />

13110<br />

13096<br />

13085<br />

834<br />

834<br />

13081 834<br />

13086<br />

13037<br />

13180<br />

13091<br />

If data errors in 834, how do we communicate the issue (e.g., DOB 1/1/1900)? How do<br />

we correct it?<br />

Current practice: phone call. Possible: outbound 834 with error code (2100 loops).<br />

Could you be specific on all scenarios where broker information will be sent in the 834<br />

and the report you will send with the applications? Also clarify how non-paid sister<br />

entities will be reported.<br />

Discrepancy and reconciliation reports are being developed. More information will be coming on<br />

these.<br />

follow up ask what the second question is<br />

834 If we will receive contractor generated group id or exchange assigned group id on 834? follow up with asker - we need more clarification to answer this question.<br />

Can we get a Trading Partner Companion guide with all the communication protocols,<br />

delimiters, actual Identifiers for ISA06 & GS02, file handling instructions, file naming<br />

conventions for SHOP/IFP, expected frequencies of in-bound/out-bound transactions<br />

and troubleshooting instructions?<br />

834<br />

trader<br />

partner<br />

agreement<br />

834<br />

Is SHOP exchange expecting contractor to generate unique group id per plan the group<br />

is enrolled in. (This requirement is called out in SHOP group setup document CMS had<br />

sent)?<br />

The draft implementation guides released last week state that CalHEERS will require a<br />

signed Trading Partner Agreement before directory testing starts 4/1/13. Can you<br />

please provide additional information about this agreement?<br />

group setup - there will be another companion guide for group setup. The Group Setup Guide is<br />

due to be posted to the bidder's library 23 April with a technical call for that date on 30 April.<br />

group setup - there will be another companion guide for group setup. The Group Setup Guide is<br />

due to be posted to the bidder's library 23 April with a technical call for that date on 30 April.<br />

more information will be available shortly<br />

Is COCC supported on the <strong>Exchange</strong>? Does the carrier need to produce the COCC for<br />

Need clarification - what is COCC?<br />

on-<strong>Exchange</strong> members or will the <strong>Exchange</strong> be handling that?<br />

Can we get a sample file with an example of how multiple ST-SE envelopes will be<br />

used?<br />

sure<br />

13191 820 When will the 820 Implementation Guide be available, and when will that testing occur? the 820 test data will be needed in June. open<br />

13107<br />

13172<br />

834<br />

9. MONTHLY RECONCILIATION - Says "QHP <strong>Issue</strong>rs will reconcile this information<br />

with their systems and report any discrepancies to Covered <strong>California</strong>." What are the<br />

remediation steps that need to occur for discrepancies sent back to the exchange?<br />

Will the discrepancies come back on an 834 or report? If report can you define the<br />

report format?<br />

At what point will Covered <strong>California</strong> determine what they will need from contractor to<br />

be ready for 7/1 go live date? Are there any additional marketing materials required in<br />

addition to plans and rates?<br />

This is a combination technical and business process question. We will provide more information<br />

soon on this.<br />

This is not a technical question. I will forward to the right folks. CalHEERS will need some<br />

brochure data - but marketing material requirements will be communicated by the marketing<br />

team.<br />

open<br />

open<br />

open<br />

open<br />

open<br />

open<br />

open<br />

open<br />

open<br />

open<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 6 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

We don‟t have information to answer the Formulary Template question at this time.<br />

We will provide information as soon as we have an update on that SERFF template.<br />

Please see the available test strategy information below:<br />

Testing with issuers will follow a two stage process.<br />

The first stage testing will include three issuers and will focus on confirming that the CalHEERS<br />

application correctly generates the outbound transactions and correctly processes the issuer‟s<br />

response. CalHEERS is scheduled to begin the coordination and planning activities with the<br />

three issuers in April. Test cases will be supplied to all issuers during the planning process.<br />

Connectivity testing is expected to occur mid to late May.<br />

• Only the 3 first stage test issuers need to provide representative test data on 15 April. No<br />

other bidders need to provide test data in April or May.<br />

13035 test strategy Are the templates that are due 4/1 to include the completion of the Rx template?<br />

• First stage testing kick off meetings will happen with each of the 3 chosen initial test issuers<br />

as soon as can be scheduled. Attendance will be technical personnel as identified by each side.<br />

Each meeting will be one on one between CalHEERS and issuers.<br />

• Transactional testing between the three issuers and CalHEERS is scheduled to begin mid-<br />

May and run through July.<br />

• Testing in June and July will utilize test data submitted by the first stage testing issuers on<br />

April 15 as well as the test data required from the rest of the issuers on June 3rd.<br />

The second stage of testing will include the remaining issuers and will focus on certifying that<br />

each issuer can process inbound transactions and generate appropriate responses. A<br />

CalHEERS testing resource will work with an issuer to identify an individual testing window. Test<br />

cases utilized during the first phase will be repurposed for certification testing. Certification<br />

testing is expected to begin on July 22 and continue through September 6.<br />

open<br />

13109<br />

13094<br />

13082<br />

834<br />

834<br />

834<br />

What will be the procedure to make an enrollment change that creates new effective<br />

dated rate computation?<br />

In the 2000 member loop Subscriber number can you identify that the qualifier 0F is<br />

used in REF01 of the HIX companion guide table?<br />

There was a comment re: "a whole bunch of ST/SE's on the response back to the<br />

<strong>Exchange</strong>". Was this re: 834 confirmation or TA1/999? What frequency would they<br />

want these bundled (daily/hourly.etc.)?<br />

we need more clarity on this question - please send more information on the question.<br />

We will follow up and get back with answer<br />

We will follow up with complete answer asap.<br />

13087<br />

834 If a dependent is added will the subscriber be carried as a passive loop in the 834? We will follow up with complete answer asap.<br />

open<br />

13089<br />

Can we get sample 834 transaction files for each enrollment scenario in section 7 of<br />

834 the companion guide?<br />

yes<br />

open<br />

13119 834 FFE 834: SSN only on initial 834. <strong>Exchange</strong>'s planned practice? Yes for the individual market. We will check for SHOP and follow up to this response. open<br />

13101<br />

On enrollment effectuation - in the 2000 REF01/REF02 Will you need to also include<br />

834 17 and 0F? yes on 17 and on 0F GI will follow up<br />

open<br />

13173 834 What is the <strong>Exchange</strong> SLA's on enrollment changes? open<br />

13177<br />

Do you have a matrix of all changes that will go through the <strong>Exchange</strong> (e.g. life<br />

changes)? How will these changes be communicated (all through the 834)?<br />

open<br />

13182 834<br />

Is the only agent/broker information captured on the consumer enrollment application,<br />

and 834, the broker name and broker account information?<br />

open<br />

13099<br />

On enrollment effectuation - Is the expectation that we would store the value sent in the<br />

834 BGN02 and send that same value back on the outbound?<br />

follow up<br />

open<br />

open<br />

open<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 7 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13121 834 Will SHOP and IFP use the same monthly reconciliation method for members?<br />

13133 834<br />

13257<br />

13104<br />

834<br />

Can we get a Trading Partner Companion guide with all the<br />

communication protocols, delimiters,<br />

actual Identifiers for ISA06 & GS02,<br />

file handling instructions,<br />

file naming conventions for SHOP/IFP,<br />

expected frequencies of in-bound/out-bound transactions and<br />

troubleshooting instructions?<br />

Wanted to follow-up on this question. Will all the data submitted by the plan be<br />

included in the physicians' or facility data. Can you provide the format the data will<br />

appear in.<br />

In 8.3 Individual Market Re-enrollment - What will the INS03 code be? No INS03 is in<br />

the CG should it be 025 - Reinstatement?<br />

group setup - there will be another companion guide for group setup. The Group Setup Guide is<br />

due to be posted to the bidder's library 23 April with a technical call for that date on 30 April.<br />

The trading partner agreement will be available prior to any connectivity testing.<br />

we need more clarity on this question - please send more information on the question.<br />

we will follow up<br />

13080 834<br />

Can we get a flow description of identifiers inbound/outbound with diagrams in the<br />

companion guide or separate document of the Trading partner IDs, BGN02/BGN06,<br />

Header REF02, QTY, Group IDs, Plan IDs, 2700/2750? We would like it to be similar<br />

to the "834 Identifiers Discussion Document" prepared by CMS for the FFE?<br />

13083 834<br />

<strong>Exchange</strong> expects single 999 for transmission. By definition 999's are at GS/GE level,<br />

does this assume they'll have one GS/GE per transmission?<br />

13092 834<br />

Currently contractor utilizes ST02 (transaction control set number) as unique group<br />

identifier sent in ST header loop for compare purposes. Will HIX use the ST02<br />

information to define each unique group? A HIX sample file would help to show how<br />

multiple groups in an 834 will sent and identified?<br />

13111 834 We assume we will receive Individual Market and SHOP 820s at the subscriber level<br />

13112 834<br />

Confirm subscriber level 820 files from SHOP will be received daily? If not, expected<br />

frequency. If we don't see a file when expected, is it an error? Note that empty files<br />

files are a bad thing.<br />

13113 834<br />

Will we see an 820 for EFT for aggregated premium payment? If so, how do we<br />

identify?<br />

13114 834 Will we see EINs in Individual Market 834s?<br />

13115 834<br />

Assume exactly 3 files per day inbound to <strong>Issue</strong>r:<br />

1) IFP 834<br />

2) SHOP 834<br />

3) SHOP 820<br />

contractor will not look for multiple files in these areas<br />

13116 834<br />

Assume exactly 3 files per day outbound from <strong>Issue</strong>r to <strong>Exchange</strong>:<br />

1) IFP 834<br />

2) SHOP 834<br />

3) IFP 820<br />

13117 834<br />

13118 834<br />

13120 834<br />

FFE plans to have unique Member ID in SHOP but we understand CA plans to use<br />

SSN in SHOP, CIN in IFP. Due to limitations on SSN as identifier, is this still planned?<br />

Verify will receive both SSN and CIN for IFP.<br />

Latest was SSN would be the ID for SHOP, but FFE is avoiding, sending only on first<br />

enrollment 834. Will CA also create a unique person ID for SHOP?<br />

SSN is required for IRS reporting for minimimum essential coverage.<br />

We assume that all employee must have SSNs, so we will always receive SSNs for<br />

subscribers<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 8 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13122 834<br />

If CA contracts out SHOP, then will we use that vendor's EDI/reconciliation or will EDI<br />

remain on the <strong>Exchange</strong> platform per <strong>Exchange</strong> protocols?<br />

13123 834<br />

Options for member reconciliation:<br />

Full file (stated in earlier discussions) - Complete roster, we act on discrepancies<br />

(enroll/autoterm to synchronize)<br />

Audit file - Generate report of discrepancies, then <strong>Exchange</strong> indicates actions to take<br />

on subsequent communication<br />

Audit file is our preferred course of action for optimal customer experience<br />

13124 834<br />

If discrepancies in membership reconciliation, we report on discrepancies.<br />

Do you review, confirm prior to our resynch?<br />

How do we resynch? Do we accept and enroll/terminate to synchronize?<br />

Terminate if not on your file? Normally we confirm first - ensure not error omit<br />

How handle timing asynchrony? Will <strong>Exchange</strong> freeze updates on a reconciliation<br />

cycle?<br />

How manage member impacts?<br />

13125 834<br />

Which elements will be reconciled (i.e., <strong>Exchange</strong> System of Record and customer<br />

must return to <strong>Exchange</strong> to update)<br />

Assume minimally<br />

Eligibility: Legal Name, Residency Address, DOB<br />

Identifiers: CIN, SSN<br />

<strong>Issue</strong>r controlled, not reliable for Member to change by contacting <strong>Exchange</strong>:<br />

<strong>Issue</strong>r ID<br />

Optional info Member may wish to vary across systems, keep private<br />

Preferred Name<br />

Preferred Contact: Current phone, current e-mail<br />

Billing info: Current billing address and/or e-payment account,<br />

third party payer name/address/contact, etc.<br />

Other Info that may change (e.g., agent transfers book of business)<br />

Broker/Agent (will impact our compensation of broker)<br />

13126 834<br />

Confirm that the HIX Group ID field is our Group ID passed back in response to XML<br />

SG Setup; we also receive EIN in its own field?<br />

Is Group ID required to be HIOS/SERFF ID? If ID changes at renewal, how do we<br />

update <strong>Exchange</strong>?<br />

13127 834 Will we get renewal 834 transaction for employee during open enrollment?<br />

13128 834<br />

Would like Producer (Agent, Broker, etc.) ID for all Individuals/Employers assisted;<br />

<strong>Exchange</strong> itself may be the "producer" or "agent"<br />

13129 834 There are both US and CA EINs; will we receive both? Where?<br />

13130 834 Confirm CA will follow CMS in using the <strong>Exchange</strong> compatible 820<br />

13131 834<br />

Will we receive renewal transactions for members who<br />

actively or<br />

passively<br />

choose to stay with their current plan?<br />

13132 834<br />

Can we get a flow description of identifiers inbound/outbound with diagrams in the<br />

companion guide or separate document of the Trading partner IDs, BGN02/BGN06,<br />

Header REF02, QTY, Group IDs, Plan IDs, 2700/2750?<br />

We would like it to be similar to the "834 Identifiers Discussion Document" prepared by<br />

CMS for the FFE?<br />

13134 834<br />

There was a comment re: "a whole bunch of ST/SE's on the response back to the<br />

<strong>Exchange</strong>". Was this re: 834 confirmation or TA1/999? What frequency would they<br />

want these bundled (daily/hourly.etc.)?<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 9 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13135 834<br />

<strong>Exchange</strong> expects single 999 for transmission. By definition 999's are at GS/GE level,<br />

does this assume they'll have one GS/GE per transmission?<br />

13136 834<br />

Need confirmation that multiple Groups/Sponsors will be represented in a single 834.<br />

Can the 834s be grouped by Sponsor? (SHOP only)<br />

13137 834 If a dependent is added will the subscriber be carried as a passive loop in the 834?<br />

13138 834<br />

Can we get sample 834 transaction files for each enrollment scenario in section 7 of<br />

the companion guide?<br />

13140 834<br />

Can we get a sample file with an example of how multiple ST-SE envelopes will be<br />

used?<br />

13141 834<br />

Currently contractor utilizes ST02 (transaction control set number) as unique group<br />

identifier sent in ST header loop for compare purposes. Will HIX use the ST02<br />

information to define each unique group? A HIX sample file would help to show how<br />

multiple groups in an 834 will sent and identified?<br />

13142 834<br />

Please clarify the broker information that will be sent in the 834 and the report you will<br />

send with the applications. Also clarify how non-paid sister entities will be reported.<br />

13143 834<br />

In the 2000 member loop Subscriber number can you identify that the qualifier 0F is<br />

used in REF01 of the HIX companion guide table?<br />

13144 834 Can you please add the DMG segment and elements used to the companion guide?<br />

13145 834<br />

Could you be specific on all scenarios where broker information will be sent in the 834<br />

and the report you will send with the applications? Also clarify how non-paid sister<br />

entities will be reported.<br />

13146 834 Will the state require TA1 on files that are good?<br />

13147 834<br />

On enrollment effectuation - Is the expectation that we would store the value sent in the<br />

BGN02 and send that same value back on the outbound?<br />

13148 834<br />

On enrollment effectuation - Will the QTY totals represent what was sent on inbound or<br />

actual totals computed from the membership being sent on the outbound?<br />

13149 834<br />

On enrollment effectuation - in the 2000 REF01/REF02 Will you need to also include<br />

17 and 0F?<br />

13150 834<br />

On enrollment effectuation - should the Maintenance Type Code for 2000 INS03 be<br />

021?<br />

13151 834<br />

On enrollment effectuation - in 2700 do we need to send back whatever is sent on<br />

inbound? Flow diagram needed.<br />

13152 834<br />

In 8.3 Individual Market Re-enrollment - What will the INS03 code be? No INS03 is in<br />

the CG should it be 025 - Reinstatement?<br />

13153 834<br />

13154 834<br />

13155 834<br />

13156 834<br />

13187<br />

In 8.4 SHOP Market Re-enrollment - Will reinstatements never occur?<br />

Reinstatements with or without a lapse, members canceled in error, etc? Would a new<br />

QHP member ID need to be generated? If so will the exchange be able to handle this?<br />

8.6. CHANGE IN CIRCUMSTANCE – SHOP ONLY - Can you explain what this<br />

means?<br />

9. MONTHLY RECONCILIATION - Says "QHP <strong>Issue</strong>rs will reconcile this information<br />

with their systems and report any discrepancies to Covered <strong>California</strong>." What are the<br />

remediation steps that need to occur for discrepancies sent back to the exchange?<br />

Will the discrepancies come back on an 834 or report? If report can you define the<br />

report format?<br />

Which dates will be sent for benefit changes - effective date will be the following day to<br />

the termination?<br />

provider directory:<br />

1) Define a provider labeled „D‟ for Dental. Just those with a DDS or DMD<br />

degree?<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 10 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

provider directory: 2) Define provider labeled „V‟ for Vision. Only those with a<br />

13188<br />

degree in Optometry (OD)? Which other degrees or specialties within MD should be<br />

considered as „V‟?<br />

general question When will be the RFP award announced as Carrier need to know<br />

13189 test strategy<br />

when they can involve in testing with CA <strong>Exchange</strong> ?<br />

13206<br />

4. Regarding the Contacts on the Administrative Data Template:<br />

a. What is the definition of the „User Access‟ contact? The person in the issuer<br />

organization who defines their user roles and responsibilities.<br />

b. What is the definition of the „APTC/CSR‟ contact? The person who is the<br />

organization SME for APTC/CSR.<br />

c. We are partnering with a dental plan for dental benefits. Who, if anyone, should<br />

be indicated for the Dental Director? all dental providers should be in your directory -<br />

each plan ID will have 1 directory.<br />

d. Is the Pharmacy <strong>Benefit</strong> Manager contact somewhat within our organization or<br />

someone at our contracted pharmacy? within your organization.<br />

e. If we are not using the On-line Enrollment Center, should the primary and backup<br />

contacts be blank? They can be blank.<br />

13207 provider dir Clarify Facility Type usage; Is there also going to a Provider type.<br />

13208 provider dir Date Created - how used and is it a constant for the file?<br />

13209 provider dir Date updated - how is this used?<br />

13210 provider dir How is a null sent - with two adjacent commas<br />

13211 provider dir What are the file rejection criteria.<br />

13212 provider dir What edits are needed for 'bad data' - eg. Alpha in an SSN.<br />

13213 provider dir Method to send file and file format. Explain more about the FTP destination<br />

13214 provider dir<br />

While the NPI is a required element, we do not have it for all providers: providers who<br />

do not bill Medicare are not motivated to provide it. Therefore it will be blank for some<br />

providers.<br />

13215 provider dir How do we handle this currently required field given this reality?<br />

13216 provider dir Item #4: How is the network ID generated?<br />

13217 provider dir Item #5: Under what circumstances is this field required to be completed?<br />

13218 provider dir Item #21: When will the list of taxonomy codes be made available?<br />

13219 provider dir<br />

Item #27: Is the expectation that plans will include providers who are retired, deceased<br />

or inactive on their files? We are assuming that we will be sending full files of active<br />

providers only.<br />

13220 provider dir<br />

Item #30: How should plans indicate on the file if a provider is contracted with more<br />

than one medical group?<br />

13221 provider dir<br />

Item #31: How should plans indicate on the file if a provider has more than one<br />

hospital affiliation?<br />

13222 provider dir<br />

Item #50 and 51: Under what circumstances are these fields required to be completed?<br />

When will the Trading Partner Agreement be released?<br />

13223 provider dir<br />

Certain Specialties are going to be displayed or are we adding all specialties that we<br />

post in our current hard copy directories<br />

13224 834 Specialty Code? What is the Specialty Code?<br />

13226<br />

trader<br />

partner When will the trader partner agreement be available?<br />

agreement<br />

13229 provider dir Is Date Created the system run date?<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 11 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13230 provider dir<br />

Is Date Last Updated in regards to any provider field that has changed from the<br />

previous version?<br />

13231 provider dir<br />

Is Data Source the health plan? Does CA HIX have a specific value they want us to<br />

use?<br />

13232 provider dir<br />

Will CA HIX require Hard Copy Directories? If they do, when are they required?<br />

During the certification period? Please explain how this is used and assigned again.<br />

13237 SERFF You mentioned that the SERFF document would assign this code, is that correct?<br />

13238 provider dir<br />

Provider Type indicator - If specialty code will determine it, What specialties qualify for<br />

'D' and 'V'? It says situational - so it is required for providers?<br />

13239 provider dir<br />

Is there any flexibility with the field lengths? This is an issue for contractor as our<br />

internal provider ids are up to 16 characters long? This is related to the PCP ID and<br />

Location IDs.<br />

13240 provider dir<br />

Also, give a little more info on the “location ID”. A site (site id) is used by multiple PCPs<br />

in contractor system. That site id is also 16 characters long in our system.<br />

13241 provider dir<br />

Under what circumstances are Items #50 and 51 these fields required to be<br />

completed?<br />

13242 provider dir<br />

The provider directory data is due to the <strong>Exchange</strong> on 6/1/13. Will <strong>Health</strong> Plans have<br />

an opportunity to update the data before the Fall open enrollment?<br />

13244 provider dir<br />

Accessibility Codes field is Varchar(1). How should this be listed when there are 6<br />

different accessibility codes?<br />

13246<br />

What format will the physician data appear in the directory. Can health plans include<br />

the physicians physician group affiliations to include with the physicians' names?<br />

13247 provider dir Clarify Facility Type usage; Is there also going to a Provider type?<br />

13248<br />

Date updated - how is this used – is it when data changed from a previous quarter for a<br />

provider?<br />

13249 How is a null sent - with two adjacent commas?<br />

13250 What are the file rejection criteria?<br />

13251 What edits are needed for 'bad data' - eg. Alpha in an SSN?<br />

13252<br />

Method to send file and file format. Explain more about the FTP destination. Is the file<br />

being sent to Enclarity?<br />

13254 provider dir<br />

For the test PD data file, how many records are deemed appropriate for each provider<br />

type?<br />

13255<br />

13256<br />

13258<br />

13260<br />

#30 for the independent network are we providing the word “Independent” or are<br />

we adding the clinic name if the provider belongs to a clinic?<br />

Will we be able to correct file errors and have them updated, or will updates have to<br />

wait until the next quarterly submission?<br />

I understood you to say that specialties would drive the value of Provider Type. Please<br />

provide a list of what specialties indicate a provider type of 'V' and what specialties<br />

indicate a provider type of 'D', so we know what value to use for this column for our<br />

providers.<br />

Our Pharmacy group has heard conflicting information on when the formulary is due to<br />

the <strong>Exchange</strong>. I have heard that the <strong>Exchange</strong> is not reviewing the formulary, so does<br />

that mean the formulary is not due until after QHP certification?<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 12 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13262 provider dir<br />

We have poured over the instructions for technical testing but cannot find answers to<br />

the following questions. I cannot tell from the Q&A on the phone whether we need to<br />

adhere to the April 1 deadline or if or if we have until April 15 to provide plan, benefit<br />

and rate data for testing? Also, under these tight timeframes, could you please provide<br />

information on the following:<br />

1. We need to sign a Trading Partner Agreement with CalHEERS to be allowed<br />

to test and be certified. Please send us the agreement and instructions.<br />

2. Complete communication connectivity testing. Please send details about the<br />

Enclarity FTP site, provide access and instructions.<br />

3. Provider Network Input file layout specific questions:<br />

a. Field 1 - Provider ID - Can this field have any length? Do you have any other<br />

specific requirements for this field?<br />

b. Field 52 - PCP ID - This field is noted as Situational and comments indicate<br />

Required for Medi-Cal Plans only. Do you want the health plan internal PCP ID (field 1)<br />

or some other PCP ID. If other, please specify what ID number is required and how<br />

this will be used to ensure contractor provides the appropriate PCP ID in field 52.<br />

c. Field 54 - Accessibility Codes - Field is defined as varchar(1). How are six<br />

different codes to be identified in the space of one?<br />

d. Field 55 - Location ID, contractor's Service Location ID will exceed 10<br />

characters. Can this field be lengthened?<br />

e. Field 56 - <strong>Issue</strong>r Name - Has a 30 character limit and contractor's issuer<br />

name is 31 characters. Can the field be extended or can contractor abbreviate? Will<br />

this field be displayed to beneficiaries?<br />

13275 test strategy Enrollment Q: When will the testing schedule for CA HIX be published?<br />

13276<br />

Contractor Q: Are details related to file transfer (file names, servers and protocols)<br />

available for all file transfers? Where are these details available?<br />

13280<br />

Will Covered <strong>California</strong> post notes/minutes on this call because the speaker is going<br />

through the material so fast that it is impossible to get everything down.<br />

13284<br />

Is the only agent/broker information captured on the enrollment application and 834 the<br />

broker name and broker ID?<br />

13285 834<br />

834 Q: In the last section of the guide, it states the a reconciliation report must be<br />

returned to Covered CA. In what form must that report be in?<br />

1. What format should the carriers use for the monthly discrepancy report?<br />

2. When can the carriers expect to receive the monthly reconciliation file?<br />

3. What will be the format of the reconciliation file from CC? Will it be a full file of<br />

active members?<br />

13286 834 834 How are we reporting back the monthly discrepancies to you?<br />

13288 834<br />

Address Changes: Does this mean you will send two iterations of the same member<br />

within one ST to SE? Or does this mean you will send two ST to SE‟s?<br />

13289 834<br />

IND Market Re-enrollment: What to do with coverage in case of subscriber death –<br />

term effective on date of death, but all effective is 1st of month?<br />

13290 834<br />

Shop: If a group cancels for nonpayment would there be no reinstatement? The topic<br />

of this webinar was the Plan guide. Will you go over this information again at the 834<br />

meeting next week?<br />

13291 834<br />

In the last section of the 834 guide, it states the a reconciliation report must be returned<br />

to Covered CA. In what form must that report be in?<br />

13292<br />

Is the only agent/broker information captured on the enrollment application and 834 the<br />

broker name and broker ID?<br />

13293 provider dir<br />

Provider directory Q: How is the exchange defining Network and how will it be used?<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 13 14 4/5/2013


Technical Interface Questions<br />

track # topic Question Response open /<br />

closed<br />

13294 provider dir<br />

13295 provider dir<br />

13296 provider dir<br />

Provider directory Q: Tier ID : Is it always concatenated to the Network ID with an<br />

underscore?<br />

Provider directory Q: Tier ID; Are the values always 1 and 2. How will Tier be defined<br />

by the exchange and how will it be used?<br />

Provider directory Q: While the NPI is a required element, we do not have it for all<br />

providers: providers who do not bill Medicare are not motivated to provide it. Therefore<br />

it will be blank for some providers. How do we handle this currently required field given<br />

this reality?<br />

13297 provider dir<br />

Provider directory Q: When will taxonomy codes and specialty codes be available? Can<br />

you confirm they will be standard CMS codes.<br />

13298 provider dir<br />

Provider directory Q: Specialty Name - Will we receive the name along with the CMS<br />

Specialty Code Standard?<br />

13299 provider dir<br />

Provider directory Q: Confirm that only active providers should be sent to the<br />

exchange.<br />

13300<br />

1. Will an SLA be given for all interfaces to and from the <strong>Exchange</strong>s,<br />

including acknowledgements?<br />

13302 834<br />

3. How will a member's premium amount be sent in the 834? Will you send the actual<br />

amount the member is responsible for. So, will subtracting the APTC from the<br />

premium amount equal the exact amount a member owes? Will the carriers be<br />

required to make any additional calculations?<br />

13303 834<br />

4. Please confirm that groups will be directed to a carrier's portal to make a payment.<br />

Once you're received a confirmation that the carrier has loaded an employer group you<br />

will send the 834 to enroll members. Also, confirm that you will not send enrollment<br />

until groups have been effectuated.<br />

13306 834<br />

2. Regarding the answer to the subscriber and the oldest person, does this apply to<br />

individual and SHOP or SHOP only?<br />

13307 834 3. What is the process for CC to receive and send APTC to members in the 834?<br />

13308 834 4. Will the carriers be required to reconcile APTC and CSR with CC.<br />

13310 FFE<br />

Are there any areas where Covered CA is going beyond the delta/baseline set by FFE<br />

guidelines?<br />

13315 SERFF When can we expect the Rate template business rules?<br />

13316 SERFF<br />

Has CA addressed the issue of validation of serff submissions with the feds? Since we<br />

are using „dummy‟ data, it may not meet criteria for validation.<br />

13318 provider dir<br />

Should we send Pharmacy network data (e.g. Pharmacies) to the <strong>Exchange</strong> in our<br />

Provider Directory in order to allow potential customers to check if a Pharmacy is in our<br />

Network?<br />

13319<br />

<strong>130405</strong> <strong>0242</strong> <strong>Open</strong> <strong>Issue</strong> <strong>Tracker</strong> 14 14 4/5/2013

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!