top of page
  • Eric Chao

Getting Started Guide


We’ve designed our entire onboarding process around the customer experience and getting started is designed to be fast and manageable for teams of any size. We accomplish this by mirroring existing operational onboarding processes for new human coding hires and leveraging your existing preferred technical integration approach. Synaptec Health does not have strict formatting requirements for our software to be able to accept encounter data.

Our engineering team takes care of all configuration and data format management upon receiving a set of sample encounters or messages. Healthcare technology should be easy to use, and we bring Silicon Valley experience and best practices to accomplish this goal.


We can complete technical integration in 2-4 weeks depending on interface / encounter file availability. Each project will have a dedicated technical and business project manager and will follow the trajectory outlined below.


Phase 1

- Define integration approach (see below)

- Share sample messaging formats and files (including output formats for billing system compatibility)

- Identify project managers

- Share custom coding guidelines, including billable procedure lists

- Complete customer agreements & BAA


Phase 2

- Establish and setup secure connection(s) depending on integration approach (SFTP, site-to-site VPN or HTTPS)

​System Configuration

- If message-based, establish site-to-site VPN and configure test messages to be sent to Synaptec Health endpoint

- If file-based, setup automated or operational transfer process

- Implement billable procedure lists, supported MIPS measures, or custom coding standards, if applicable


Phase 3

- Validate connectivity and trigger test messages / encounters

- Setup network monitoring and support

- Identify go-live date(s)

- Define and run end-to-end testing

- Share and review initial coding results

- Apply coding standards adjustments

- Troubleshoot any issues


​- Communicate setup and workflows to operational teams

- End-user support


Phase 4

​- Update configurations to production

- Enable production interface feeds

- Troubleshoot any issues

- End-user support

Integration Approaches

We accept messages and encounter data via HL7 / CSV / RTF / PDF / JSON and other standard formats. We work with your preferred and existing endpoints (socket based, restful APIs or SFTP) including conforming to EHR vendor specific specifications or working with your existing integration engine. Your coding results can also be returned via any of the following as well.

Flat Files

- Securely upload patient encounter files via SFTP and we'll handle any required data format translations.

- We accept any structured data formats including HL7 / CSV / RTF / PDF / JSON and other binary formats including for your demographic files and charge sheets


- Push your existing HL7 (or other) formatted messages / files directly to our secure endpoint over a site-to-site VPN via TCP/IP (or other)


- Synaptec Health connects directly to your restful API (FHIR or other) to retrieve the required encounter and demographic data required for coding

Synaptec Health Data Requirements

The following is a summary of the Synaptec Health data requirements for coding and MIPS.


​- Patient Name

- Patient ID / MRN

- Account Number / CSN

- Sex

- DOB / Age

- Arrival route / time

- Facility ID / Place of service

- Hospice status


- Chief Complaint

- History of Present Illness

- PFSH (including medical, medication, allergy, immunization, family, social and surgical history)

- Review of Systems

- PE (including vitals, blood pressure screens)

- Medical Decision Making

- Diagnosis (including any pre-selected ICD-10 codes)

- Orders including:

- Labs & Studies (lab orders & results)

- Medications

- Imaging (imaging orders & results - including EKGs if separate)

- Supplies (if applicable)

- Procedures


- Note author(s) & provider type(s)

- Attestation statements

- Record review (if applicable)

- Scribe (if applicable)

- Signature(s)


- Primary Insurance (type, plan and subscriber)

- Secondary Insurance (type, plan and subscriber)


- Discharge instructions

- Discharge medications

- Discharge route


- Note status (Primary, amended / addendum)

- Chart in Error

- Encounter Date / Time

Next Steps

We can share our detailed technical getting started checklist and standard BAA.

Designated Technical Points of Contact:

Chris McLaughlin (415) 702-0368

Eric Chao (732) 841-6033


bottom of page