Colorado Medicaid EDI Enrollment Checklist for Health First Colorado

Last reviewed: October 20, 2026 · Written by the Web Mavens healthcare engineering team

This is the checklist we wish we'd had when we enrolled our own claims application as a Health First Colorado (Colorado Medicaid) EDI trading partner. It covers who actually needs a Trading Partner ID, the enrollment tasks in the Edifecs/Cotiviti portal, SFTP setup, file naming, the companion guides, and what to watch after go-live.

Everything process-specific below comes from the Colorado Department of Health Care Policy and Financing (HCPF) pages linked in each section and in the sources. HCPF changes these pages often, so treat their current version as the final word.

Already submitting with a Trading Partner ID? HCPF has moved X12 file exchange to a new Trading Partner Enrollment and Testing Site. According to its EDI Support page, every trading partner that submits X12 transactions must finish enrollment there by October 30, 2026: compliance testing, a new trading partner agreement and a new SFTP connection. Access to the old MOVEit server is revoked after that, and files stored there don't move over, so download your 999 and 835 files first.

1. Decide whether you need your own Trading Partner ID

A Trading Partner ID (TPID) is for the organization that actually sends and receives batch X12 files. Not every provider needs one. HCPF's EDI FAQ says providers that use a third-party trading partner or clearinghouse should tell that partner about changes, but don't need to enroll themselves. Single, interactive claims are entered by providers in the Provider Web Portal, not sent by trading partners.

Option	Who enrolls as a trading partner	Usually fits when
Provider Web Portal	Nobody. The provider keys claims in one at a time.	Low claim volume and no need for claim data in your own system.
Clearinghouse or billing agent	The clearinghouse or billing agent. You authorize it to submit for you.	You bill many payers and want one connection for all of them.
Your own TPID (direct)	Your organization, or the software vendor that runs your claims application.	Medicaid is a large share of your claims, or you want 999s, claim responses and 835s to land directly in your own software.

Plenty of organizations go direct for Medicaid and use a clearinghouse for everyone else. There's no single right answer.

2. Before you start

The providers you'll bill for are enrolled with Health First Colorado. HCPF's instructions for authorizing a trading partner and for 835 enrollment only work for providers already approved in Colorado interChange, the state's claims payment system.
A business email address. If you're an existing trading partner, register with the email already on file for your TPID; that's how the existing ID is kept. HCPF asks you to confirm it with the Provider Services Call Center first. A different email can produce a brand-new TPID (Registration Guide, EDI FAQ).
An authenticator app. Multi-factor authentication is required. HCPF recommends PingID and also accepts Google Authenticator, Okta and Microsoft Authenticator.
An SFTP client or a scripted connection. FileZilla or WinSCP works for setup and testing. For production, most teams automate transfers from their own application.
The X12 implementation guides (TR3s). Colorado's companion guides assume you've bought and are familiar with the ASC X12 TR3 for each transaction. The companion guides only list Colorado-specific rules on top of them.
De-identified test files. Compliance test files shouldn't contain PHI. Build a small set of realistic but fake claims for each transaction type you plan to send.
Someone who can sign the trading partner agreement. Any authorized representative of your organization, or the account administrator, can sign it.

3. Register on the Trading Partner Enrollment and Testing Site

The enrollment site is Cotiviti Smart Trading Cloud (Edifecs). HCPF's Trading Partner Registration Guide walks through each screen. In short:

Sign up with your business email. With an organizational domain, choose Trading Partner as the organization type and enter your organization details.
Confirm your email from the link HCPF's system sends you. If the link expires, register again.
Turn on multi-factor authentication under My Profile and pair your authenticator app.
New trading partners complete Register New Partnership with business type Trading Partner. Existing trading partners skip this. Each new partnership gets a new TPID, so don't create one you don't need.
The first person to register becomes the administrator and can add other users from My Organization Profile → User Management. Accounts lock after three wrong passwords.

4. Complete the seven enrollment tasks

Inside the site, enroll in the Trading Partner Enrollment & Testing program. Its tasks must be done in order. This summary follows HCPF's Trading Partner Enrollment and Testing Program Guide.

File Exchange Question. Say whether you'll send and receive files (for example 837s and 270s), or only receive them (for example 834s and 820s).
Trading Partner Agreement. Read and e-sign it. Existing trading partners must sign the new agreement too.
Resources. Review the companion guide and the file naming standards, and check that the right TPID shows under My Organization Profile. It can take 15 to 30 minutes to appear after a change.
Compliance Validation. Upload a test X12 file of ten transactions or fewer, with no PHI, for each file type you'll submit. At least one file has to pass. Failed runs come with downloadable validation reports. When you're done, submit for approval. HCPF says to allow up to one business day for the EDI team to approve.
Managed File Transfer (MFT) setup. Add the trusted user emails and choose either a standard SFTP connection or the MFT Agent. Authentication is by SSH key only; passwords aren't supported. You can use an MFT-generated key pair or upload your own public key. Each time you download the generated key, the previous one stops working.
MFT connectivity test (send). Drop a correctly named test file into the toedifecs folder. It should be picked up within seconds. If an error file appears instead, it's usually the file name.
MFT connectivity test (receive). Look for a response file in the fromedifecs folder. A rsp.txt means success; a rjct.txt usually means the TPID in the file name is wrong. HCPF suggests waiting about ten minutes before you troubleshoot.

After the last task, HCPF says the Enrollment Approval Letter arrives at your registered email within one business day, and the new SFTP is ready for production files by 8 a.m. Mountain Time the next calendar day. Don't submit the final task until you're ready to switch over.

5. Get file naming and envelopes right

File names are where most early rejections come from. HCPF's X12 File Naming Standards Quick Guide requires this pattern:

TPID-TransactionType-yyyymmddhhmmssSSS-1of1.x12

The TPID is prefixed with TP, with no hyphen or underscore between them, and matches ISA06.
Claims need the type letter: 837P, 837I or 837D. Other examples are 270 and 276.
The timestamp is all 17 digits, including three for milliseconds, in 24-hour Mountain Time.
1of1 is the only accepted value, and the extension is .x12.
Use hyphens between parts only. Underscores and other special characters aren't allowed.

Inside the file, the 837P companion guide sets the receiver to COMEDASSISTPROG in ISA08 and GS03, puts your TPID in ISA06 and GS02, and uses payer ID CO_TXIX. It also allows a single ISA per file, limits each ST–SE transaction to 5,000 claims, and requires fee-for-service and encounter claims to go in separate batches. Check the guide for your claim type before you build: details like these differ between 837P and 837I.

HCPF also asks trading partners to combine claims into one batch file rather than sending many single-claim files, which can slow processing. The EDI FAQ lists a 10 MB upload limit.

6. Transactions and companion guides

Each Colorado companion guide supplements the national X12 standard. They're revised regularly, so check the version date before every build.

Transaction	What it's for	Colorado notes
837P	Professional claims	837P companion guide (005010X222A1)
837I	Institutional claims	837I companion guide (005010X223)
837D	Dental claims	Supported in the file naming standard. Get the current guide from HCPF's EDI resources or the enrollment site.
999 and TA1	Acknowledgments that your file was received and passed syntax checks	A 999 comes back for every file. A TA1 depends on ISA14, and an HTML error report is added only when there are errors.
277	Claim status responses	Returned to your SFTP as response files
835	Electronic remittance advice	835 companion guide (005010X221). Each provider has to point its 835 enrollment at your TPID (see step 7).
270/271	Eligibility inquiry and response	270/271 companion guide (PDF) (005010X279)
276/277	Claim status inquiry and response	276/277 companion guide (PDF) (005010X212)
834 and 820	Enrollment and premium payment files	Receive-only transactions, mainly for health plans

Real-time eligibility through the Safe Harbor web service is a separate arrangement. HCPF says trading partners already approved for it keep that access, while batch 270s move to the new MFT/SFTP.

7. Steps your providers complete

If you submit for providers other than yourself, a couple of steps happen on their side, in the Provider Web Portal. Build them into your onboarding checklist, because claims can't flow until they're done.

Authorize you as their submitter. HCPF's TPID authorization instructions (PDF) have the provider add you under Manage Accounts → Add Registered Billing Agent/Clearinghouse/Switch Vendor using your nine-digit TPID. Those instructions were last revised in 2023, so check HCPF for a newer version.
Send their 835s to you, if you want remittance. The provider completes the ERA (835) Enrollment Application in the Provider Web Portal with your TPID (Updating ERA 835). The change takes effect right away, but the first 835 arrives after the next financial cycle that includes claim activity.
Providers with their own TPID link it to their portal account under My Profile → Add Role and Manage Accounts → Link Registered Trading Partner ID for X12 Reports (Link the TPID).

8. Pharmacy (NCPDP) claims: confirm your route

Pharmacy claims aren't sent as X12 837 files; they use NCPDP formats instead. Real-time, point-of-sale Health First Colorado fee-for-service pharmacy claims are processed in the NCPDP Telecommunication Standard D.0 format, and since April 1, 2026 the pharmacy benefit manager processing them has been MedImpact, replacing Prime Therapeutics (HCPF PBM change notice, PBMS transition).

The field-level rules are in the MedImpact Colorado Medicaid payer sheet. It lists BIN 018902, PCN P303018902 and group COMEDICAID, and D.0 is the only version supported.
HCPF's notice says the BIN, PCN and group didn't change in the transition. If claims stop routing, it tells pharmacies to check with their switch vendor.
Fields are edited against the NCPDP standard even when they're optional. The notice gives examples: patient ZIP codes without dashes, and cardholder names and street addresses in capital letters.
Medicaid managed care plans have their own pharmacy contacts and drug lists, listed on HCPF's Pharmacy Resources page.

Point of sale isn't the only route. Batch NCPDP submissions can also be sent through a trading partner connection. In our experience this works in production: we build and run a Laravel application that submits a Colorado pharmacy's NCPDP claims in batch over its trading partner SFTP connection, alongside its 837P files.

If you build pharmacy software, decide early which route each claim type takes, because the specs differ. Real-time claims follow the MedImpact payer sheet and your switch vendor's requirements. Batch files sent through a trading partner connection follow the enrollment, testing and file naming steps above. HCPF revises both, so confirm your route and format against the current companion guides and payer sheet, or with HCPF EDI support, before you build. Any X12 files you also exchange with Health First Colorado, such as 270/271 eligibility checks, go through the trading partner process too.

9. Go-live and ongoing monitoring

Start small. Send a small first production batch and check every 999 and claim response before you increase volume.
Match every file to an acknowledgment. HCPF says most files get a response within about two hours, and larger ones can take longer. Alert on any file that has no 999 well past that point.
Track claims at the claim level. The patient control number you assign comes back on the 835. The Internal Control Number (ICN) that interChange assigns identifies each claim inside a batch, and you'll need it for adjustments and voids (frequency codes 7 and 8 in the 837P guide).
Treat the SFTP key like a password. Store it in a secrets vault, not in code. Remember that downloading a new key invalidates the old one, so plan rotations.
Watch HCPF's announcements. The EDI Support page posts "Communications to Submitters" notices. Recent ones include the file naming change that took effect in January 2026 and the 2026 move to the new enrollment site.
Re-read the companion guides when they change. A dated copy of the version you built against makes regressions much easier to trace.
Keep PHI out of logs. Claim files are PHI. Keep them out of application logs, error trackers and staging data, and sign a BAA with anyone who handles them.

When you need help, HCPF's EDI Support page tells trading partners to call the Provider Services Call Center and say "EDI" to reach the right queue.

Want claims to go out from your own software?

We built and enrolled a Laravel claims application as a Health First Colorado trading partner. If you'd rather have 837s, 999s and 835s handled inside the system your team already uses, see how we approach Medicaid EDI claims integration. We'll also tell you honestly when a clearinghouse is the better choice.

See our Medicaid EDI integration service

Sources

All checked on October 20, 2026. This page is general guidance, not legal or billing advice. Where it differs from HCPF's current documents, follow HCPF.