Profee Coding Specialist - REMOTE
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
Content:
- About Us: description of purpose, etc. Could be "About the role"? Actually "About Us" is company description. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading, but we have "About Us". Might map to "About the role"? The instruction says use those headings as examples; we can use similar headings. Probably we should use "About the role" for company overview? Or we could use "About Us" but they said use those examples; but they didn't forbid other headings? They said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those exact headings if content exists. We have content about company purpose, mission, etc. That could go under "About the role"? Not exactly. Maybe we can create "About the role" heading and put the company description there. Or we could skip that section if not matching exactly. But we need to preserve all substantive information. So we need to include company description somewhere. Could put under About the role
.
Then "Job Summary" could be part of About the role as well.
Then "Essential Duties And Responsibilities" -> Responsibilities section.
Then "Minimum Qualifications & Requirements" -> Requirements/Qualifications/Skills. We need to decide which headings to use. There's "Minimum Qualifications & Requirements" includes certifications, experience, attendance, systems knowledge, phone/internet, productivity, quality, Microsoft proficiency, communication, etc. That's qualifications and requirements. Could split into Requirements (certifications, experience) and Skills (Microsoft, communication). But we can combine into one section "Requirements". However we also have "Physical Demands" which could be part of Requirements or maybe a separate section? Not in list. Could be omitted? But we need to preserve all substantive info. Physical Demands is substantive. Could be placed under a heading like "Requirements" as well, or maybe we create a section "Physical Demands". But the instruction says prefer a few substantive sections over many thin ones. So we could include Physical Demands within Requirements or maybe a separate "Physical Demands" section if we think it's substantive enough. But they didn't list Physical Demands as a possible heading; but we can still use for any section heading? They said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should limit to those headings. So we should map content to those headings. Physical Demands could go under Requirements (as it's a requirement). Or maybe under Qualifications. We'll decide.
We also have "Note: Reasonable accommodations..." etc. That's part of Physical Demands.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none evident.
We must not repeat job title as heading. Not needed.
We must not put Job ID/requisition numbers as headings.
We must not include sections with filler like "commensurate with experience". Not present.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does not mention pay, schedule, benefits. So we should NOT include those sections.
Thus we will have sections: About the role, Responsibilities, Requirements (maybe also Qualifications/Skills). But we need to avoid thin sections. Could combine Qualifications and Skills into Requirements.
Let's structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those exact headings if content exists. We have content about company purpose, mission, etc. That could go under "About the role"? Not exactly. Maybe we can create "About the role" heading and put the company description there. Or we could skip that section if not matching exactly. But we need to preserve all substantive information. So we need to include company description somewhere. Could put under About the role
.
Then "Job Summary" could be part of About the role as well.
Then "Essential Duties And Responsibilities" -> Responsibilities section.
Then "Minimum Qualifications & Requirements" -> Requirements/Qualifications/Skills. We need to decide which headings to use. There's "Minimum Qualifications & Requirements" includes certifications, experience, attendance, systems knowledge, phone/internet, productivity, quality, Microsoft proficiency, communication, etc. That's qualifications and requirements. Could split into Requirements (certifications, experience) and Skills (Microsoft, communication). But we can combine into one section "Requirements". However we also have "Physical Demands" which could be part of Requirements or maybe a separate section? Not in list. Could be omitted? But we need to preserve all substantive info. Physical Demands is substantive. Could be placed under a heading like "Requirements" as well, or maybe we create a section "Physical Demands". But the instruction says prefer a few substantive sections over many thin ones. So we could include Physical Demands within Requirements or maybe a separate "Physical Demands" section if we think it's substantive enough. But they didn't list Physical Demands as a possible heading; but we can still use for any section heading? They said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should limit to those headings. So we should map content to those headings. Physical Demands could go under Requirements (as it's a requirement). Or maybe under Qualifications. We'll decide.
We also have "Note: Reasonable accommodations..." etc. That's part of Physical Demands.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none evident.
We must not repeat job title as heading. Not needed.
We must not put Job ID/requisition numbers as headings.
We must not include sections with filler like "commensurate with experience". Not present.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does not mention pay, schedule, benefits. So we should NOT include those sections.
Thus we will have sections: About the role, Responsibilities, Requirements (maybe also Qualifications/Skills). But we need to avoid thin sections. Could combine Qualifications and Skills into Requirements.
Let's structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should limit to those headings. So we should map content to those headings. Physical Demands could go under Requirements (as it's a requirement). Or maybe under Qualifications. We'll decide.
We also have "Note: Reasonable accommodations..." etc. That's part of Physical Demands.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none evident.
We must not repeat job title as heading. Not needed.
We must not put Job ID/requisition numbers as headings.
We must not include sections with filler like "commensurate with experience". Not present.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does not mention pay, schedule, benefits. So we should NOT include those sections.
Thus we will have sections: About the role, Responsibilities, Requirements (maybe also Qualifications/Skills). But we need to avoid thin sections. Could combine Qualifications and Skills into Requirements.
Let's structure:
About the role
Our purpose is to help clients exceed their financial health goals. Across the reimbursement cycle, our scalable solutions and clinical expertise help solve programmatic needs. Enabling our teams with leading technology allows analytics to guide our solutions and keeps us accountable achieving goals. We build long-term careers by investing in YOU. We seek to create an environment that cultivates your professional development and personal growth, as we believe your success is our success.
Job Summary: Coding Specialists are an important part of the Team at CorroHealth. The Coding Team Member will provide CPT, HCPCS and ICD-10-CM coding a minimum of 1-4 specialties. Specialties needed: Primary care, Trauma, Neuro and Ortho.
Then Responsibilities:Responsibilities
- Provide various components of coding services to support our clients.
- Calculate ProFee levels by using an algorithm created by our company.
- Recognize critical care cases by patient acuity.
- Experience with the following specialties: Primary Care, Trauma, Orthopedic, Neurology.
- Apply ICD-10-CM diagnosis codes to the highest level of specificity available.
- Accurately apply diagnosis and procedure codes utilizing ICD-10-CM, ICD-10-PCS, CPT®, and HCPCS.
- Interpret coding guidelines for accurate code assignment.
- Identify the importance of documentation on code assignment and the subsequent reimbursement impact.
- Align conduct with AHIMA's Standards of Ethical Coding and the Company’s Code of Ethics and Business Conduct and support the Company’s Ethics and Compliance Program.
- Comply with all internal policies and procedures.
- Actively participate in Company provided training and education.
- All Coders must maintain at least one credential through either AAPC or AHIMA.
- Ensure individual compliance with all privacy and security rules and regulations and commit to the protection of all Company confidential information, including but not limited to, Personal Health Information.
Requirements
- Certified through either the AAPC (CPC or COC) or AHIMA (CCS or CCS-P).
- Minimum of 2 years of on‑the‑job coding experience.
- Regular, predictable, and punctual attendance required.
- Working knowledge and experience with systems such as EMR, billing, etc.
- Must have a phone, reliable internet connection, and current coding materials (CPT, ICD‑10‑CM references).
- Maintain an ongoing productivity level and accuracy rate of 95% or higher.
- Maintain a quality score of 95% or higher.
- Proficient in Microsoft programs like Excel and Outlook (able to open/edit spreadsheets, perform basic formulas, manage email and schedule meetings).
- Ability to communicate effectively and professionally, both verbally and in writing.
- Ability to coordinate, analyze, observe, make decisions, and meet deadlines.
- May be required to perform other duties as assigned by leadership.
- Physical demands: regular eye‑hand coordination and manual dexterity to operate office equipment; ability to work at a computer terminal 6‑8 hours per day with constant interruptions; frequent prolonged sitting; occasional lifting/moving up to 20 lbs.; potential for elevated stress during peak activity and multiple deadlines.
before the list. Similarly, there is a note in Physical Demands: "Note: Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions as described." That's substantive; we should include. Also there is a note at end: "A job description is only intended as a guideline and is only part of the Team Member’s function. The company has reviewed this job description to ensure that the essential functions and basic duties have been included. It is not intended to be construed as an exhaustive list of all functions, responsibilities, skills and abilities. Additional functions and requirements may be assigned by supervisors as deemed appropriate." That's also substantive; we should include. Thus we need to incorporate those notes. Let's restructure: About the role: include company purpose and job summary. Responsibilities: include the note about essential duties not exhaustive, plus