Browse categories
Explore
Fiverr Pro
English
$
USD
Looks Like This Service Is On Hold
I will provide healthcare edi support, debugging, and issue fixing
Adil Javed
About this gig
I provide senior-level healthcare EDI support and production workflow stabilization for clearinghouse, payer, and billing environments. My approach focuses on root-cause analysis, structured debugging, and corrective guidance that improve reliability, reduce rejections, and support long-term RCM performance.
Supported EDI transactions:
- 837P / 837I / 837D (Claims)
- 835 (Remittance)
- 270 / 271 (Eligibility)
- 276 / 277 (Claim Status)
- 275 (Attachments), 278 (Referrals/Authorizations)
Consulting focus areas:
- Production validation, parsing, and loop/segment issues
- Mapping corrections and data-quality alignment
- Connectivity and workflow stability (batch & real-time)
- Clearinghouse and payer rejection interpretation
Technology capability:
- C#/.NET, Java, Node.js
- APIs & Salesforce integrations
- RabbitMQ, Kafka (queue-based workflows)
- SQL, MongoDB, MySQL, and NoSQL database platforms
Support models available:
- One-time issue support
- Weekly engineering assistance
- Monthly ongoing stability & optimization
Please contact me before ordering to discuss your issue, environment, and objectives.
Get to know Adil Javed
Adil Javed
Healthcare EDI and RCM Automation Developer with FHIR Expertise
- FromPakistan
- Member sinceMar 2018
- Avg. response time10 hours
Languages
English
Healthcare EDI and RCM Automation Developer with FHIR expertise and 14+ years delivering production EDI, API and clearinghouse solutions for providers, billing teams and healthtech platforms
• EDI parsing, validation, and debugging
• CMS-1500 to EDI mapping and crosswalks
• Claims 837P 837I 837D, 835, TA1 997 999 277CA
• Eligibility 270 271, Claim Attachment 275, Claim Status 276 277, Referrals 278
• Realtime and batch clearinghouse and multi-payer integrations
• Claim scrubber and automation
• Workers comp EDI, FHIR and custom APIs
I build, improve and fix EDI workflows and production systems
FAQ
Do you only provide guidance, or do you also fix issues?
Where feasible, I implement minor fixes, mapping corrections, and workflow adjustments as part of the engagement. If the issue requires larger development or architectural changes, I will recommend a scoped upgrade or implementation plan.
Which systems and environments do you support?
I support EDI and RCM workflows across clearinghouse, payer, billing, and provider environments, including API-based integrations, database-driven workflows, and message-queue pipelines.
Do you work with custom or non-standard EDI formats?
Yes. I can review custom layouts, proprietary schemas, and vendor-specific variations, as long as a sample file and rejection details are provided.
Can you help with clearinghouse or payer rejections?
Yes, I review rejection details in workflow context, identify the root cause, and provide corrective guidance or fixes to help the file pass successfully.
What is included in the one-time, weekly, and monthly support plans?
One-time support → Single issue or failed file Weekly support → Multiple issues within the same week Monthly support → Ongoing stability, recurring fixes, and workflow monitoring Scope remains focused on support, debugging, and corrective actions.
Do you modify production systems directly?
Direct system changes may be performed where safe and feasible. For larger code or workflow modifications, I recommend a structured development upgrade to avoid operational risk.
Which EDI transactions do you support?
837P / 837I / 837D, 835, 270 / 271, 276 / 277, 275, 278 and related X12 healthcare files.
What information do you need before starting?
Please share: Sample EDI file(s) or logs Error or rejection message Workflow context (payer, clearinghouse, billing system) Expected outcome or goal
