Jobs · Finance · Minnesota

Claims Specialist

Park Nicollet Health Services · St Louis Park, MN · 1 mo ago
FinanceFull-time
We need to output HTML fragment with sections only if real content. The posting includes: Position Summary (description), Required Qualifications (list), Preferred Qualifications (list), Benefits (description), About Us (description), Benefits Designed To Support Your Total Health (maybe duplicate benefits). Also there is mention of "Benefits" earlier. We need to avoid duplicate sections. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content to appropriate headings. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? Probably yes: we can use those headings as appropriate. We must not repeat job title as heading. Also we should not include Pay or Schedule unless posting states them. No pay or schedule info given, so omit those sections. We need to decide which sections to include: About the role (maybe position summary). Responsibilities (maybe specific assignments). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications). Skills (maybe knowledge, skills, abilities). Benefits (benefits description). About Us maybe could be under About the role? But we have heading "About the role". Could also include "About Us" as separate? Not in list but we could still use heading "About the role" for position summary and maybe "About Us" as separate? The instruction says use those headings as examples, not strict list? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should use those headings where applicable. So we can have sections: About the role (position summary), Responsibilities (specific assignments), Requirements (required qualifications), Qualifications (preferred qualifications), Skills (knowledge, skills, abilities), Benefits (benefits description). Possibly also About Us could be under About the role or maybe we could add a section "About Us" but not in list; maybe we should avoid extra headings not listed. Better to incorporate About Us into About the role or maybe as a separate paragraph under About the role? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to stick to those. Thus we need to extract content: Position Summary: "This position ensures that insurance and other 3rd party claims are submitted and/or paid in a timely manner and are compliant with applicable regulations and payer requirements. Specific assignments may include pre-adjudication and/or follow-up, facility and/or professional claims, commercial and/or government payers. Effective performance of these functions helps the organization achieve strong cash flow and maximize patient satisfaction." We can split: About the role: first sentence maybe. Responsibilities: specific assignments sentence. Required Qualifications: list: "Requires strong attention to detail and demonstrated problem resolution skills. Must be able to effectively communicate verbally and via written documents. Moderate personal computer proficiency with word processing, spreadsheets and email is required (preference for Microsoft Suite). Working knowledge of typical office equipment is expected." Preferred Qualifications: list: "Experience in a health care revenue cycle environment preferred. Knowledge, Skills, And Abilities Ability to acquire and retain complex knowledge of department/company processes, government policy/regulation, and payer requirements. Prior medical terminology and procedural/diagnostic coding (CPT, ICD) knowledge will be helpful. Proficiency with Health Information Systems (e.g., Epic) preferred." But note the Preferred Qualifications section includes a heading "Knowledge, Skills, And Abilities" inside; we might treat that as Skills section. Skills: maybe combine knowledge, skills, abilities from both required and preferred? The posting has "Knowledge, Skills, and Abilities:" under Required Qualifications, then later "Knowledge, Skills, And Abilities" under Preferred Qualifications. We could create a Skills section that includes those bullet points. But we need to avoid duplication. Let's parse: Required Qualifications block includes: - Knowledge, Skills, and Abilities: Requires strong attention to detail and demonstrated problem resolution skills. Must be able to effectively communicate verbally and via written documents. Moderate personal computer proficiency with word processing, spreadsheets and email is required (preference for Microsoft Suite). Working knowledge of typical office equipment is expected. Preferred Qualifications block includes: - Education, Experience or Equivalent Combination: Experience in a health care revenue cycle environment preferred. - Knowledge, Skills, And Abilities Ability to acquire and retain complex knowledge of department/company processes, government policy/regulation, and payer requirements. Prior medical terminology and procedural/diagnostic coding (CPT, ICD) knowledge will be helpful. Proficiency with Health Information Systems (e.g., Epic) preferred. Thus we could have: Requirements (Required Qualifications) as list. Qualifications (Preferred Qualifications) as list (education/experience). Skills (Knowledge, Skills, Abilities) combine both sets? Might be redundant but we can include both sets under Skills. But we must not create thin sections. Let's see if we have enough content for each. About the role: we have position summary sentence. Responsibilities: we have specific assignments sentence. Requirements: we have required qualifications list (4 items). Qualifications: we have preferred qualifications list (education/experience plus maybe some other). Actually preferred qualifications includes education/experience and also knowledge, skills, abilities. But we already have Skills separate. Benefits: we have benefits description (two paragraphs about benefits). We'll combine. We should not include About Us unless we have a heading for it; we could incorporate into About the role maybe as additional paragraph. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine About Us into About the role or maybe we omit it. However About Us contains substantive info about organization; we could include as a separate section "About the role" maybe not appropriate. Could we use "About the role" for position summary and "About Us" as separate heading? Not in list but maybe allowed. Safer to omit About Us to avoid extra heading not listed. But we risk losing substantive info. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep About Us info. If we don't have a heading for it, we could put it under a generic

without heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. We could still use

for About Us, but it's not in the list; maybe it's okay as long as we use

. The examples are not exhaustive. So we could add About Us heading. Thus sections: About the role (position summary), Responsibilities (specific assignments), Requirements (required qualifications), Qualifications (preferred qualifications), Skills (knowledge, skills, abilities), Benefits (benefits description), About Us (organization description). That seems reasonable. We must not include Pay or Schedule. Now format: each heading

Heading

then content: if list, use
  • ... etc. If prose, use

    . We need to preserve all substantive information, not invent or summarize away detail. So we need to copy the text exactly as given, but we can split into list items. Let's extract exact sentences. Position Summary paragraph: "This position ensures that insurance and other 3rd party claims are submitted and/or paid in a timely manner and are compliant with applicable regulations and payer requirements. Specific assignments may include pre-adjudication and/or follow-up, facility and/or professional claims, commercial and/or government payers. Effective performance of these functions helps the organization achieve strong cash flow and maximize patient satisfaction." We can split: first sentence for About the role, second sentence for Responsibilities, third sentence maybe also part of Responsibilities or About the role? Could be part of Responsibilities as outcome. We'll keep third sentence maybe under Responsibilities as well. Thus About the role: "This position ensures that insurance and other 3rd party claims are submitted and/or paid in a timely manner and are compliant with applicable regulations and payer requirements." Responsibilities: "Specific assignments may include pre-adjudication and/or follow-up, facility and/or professional claims, commercial and/or government payers. Effective performance of these functions helps the organization achieve strong cash flow and maximize patient satisfaction." Now Required Qualifications block: The text after "Required Qualifications Knowledge, Skills, and Abilities:" includes: "Requires strong attention to detail and demonstrated problem resolution skills. Must be able to effectively communicate verbally and via written documents. Moderate personal computer proficiency with word processing, spreadsheets and email is required (preference for Microsoft Suite). Working knowledge of typical office equipment is expected." We need to make list items. Each sentence could be a list item. Thus

    • Requires strong attention to detail and demonstrated problem resolution skills.
    • Must be able to effectively communicate verbally and via written documents.
    • Moderate personal computer proficiency with word processing, spreadsheets and email is required (preference for Microsoft Suite).
    • Working knowledge of typical office equipment is expected.
    Now Preferred Qualifications block: after "Preferred Qualifications Education, Experience or Equivalent Combination:" we have: "Experience in a health care revenue cycle environment preferred. Knowledge, Skills, And Abilities Ability to acquire and retain complex knowledge of department/company processes, government policy/regulation, and payer requirements. Prior medical terminology and procedural/diagnostic coding (CPT, ICD) knowledge will be helpful. Proficiency with Health Information Systems (e.g., Epic) preferred." We need to parse: It seems there is a run-on: "Experience in a health care revenue cycle environment preferred. Knowledge, Skills, And Abilities Ability to acquire and retain complex knowledge of department/company processes, government policy/regulation, and payer requirements. Prior medical terminology and procedural/diagnostic coding (CPT, ICD) knowledge will be helpful. Proficiency with Health Information Systems (e.g., Epic) preferred." We could split into list items: - Experience in a health care revenue cycle environment preferred. - Ability to acquire and retain complex knowledge of department/company processes, government policy/regulation, and payer requirements. - Prior medical terminology and procedural/diagnostic coding (CPT, ICD) knowledge will be helpful. - Proficiency with Health Information Systems (e.g., Epic) preferred. Note the phrase "Knowledge, Skills, And Abilities" appears as a heading but we treat it as part of the sentence; we already have Skills section separate. Might duplicate. But we could still include it as a qualification item. Now Skills section: we need to capture knowledge, skills, abilities from both required and preferred? The required already had knowledge, skills, abilities bullet points (attention to detail, communication, computer proficiency, office equipment). The preferred also had ability to acquire knowledge, medical terminology, proficiency with Epic. We could combine all under Skills. But we already used those in Requirements and Qualifications. To avoid duplication, maybe we should not duplicate. The instruction says preserve ALL substantive information; duplication is okay if it's in original? But we should not invent or summarize away detail. Duplicating is preserving detail but may be redundant. However we could keep them only once under appropriate sections. The required qualifications already cover attention to detail, communication, computer proficiency, office equipment. The preferred qualifications cover experience, ability to acquire knowledge, medical terminology, Epic proficiency. So we could put those under Qualifications (preferred) and Skills maybe not needed. But we have a Skills heading in the list; we could decide to omit Skills if content is thin. However we have content for Skills: the knowledge, skills, abilities from required and preferred. But we already used them. Perhaps better to have Skills section that includes the knowledge, skills, abilities statements (both sets) and not duplicate them elsewhere. Then Requirements and Qualifications sections would focus on other items like education/experience. Let's

Similar jobs

Claims Specialist

SECO Energy (Sumter Electric Cooperative)Sumterville, FL· 4 days ago
Financeapply on secure3.entertimeonline.com

Claims Specialist

FNIC Trusted insurance advisorsOmaha, NE· 1 mo ago
Finance$250k/yrapply on recruiting.paylocity.com

Claims Specialist

ACERTUSOverland Park, KS· 1 mo ago
Finance$22–$24/hrapply on recruiting2.ultipro.com

Claims Specialist

Brown & BrownUnited States· 1 mo ago
RemoteFinance$18/hrapply on bbinsurance.wd1.myworkdayjobs.com

Claims Specialist

One80 IntermediariesUnited States· 1 mo ago
RemoteFinance$18/hrapply on bbinsurance.wd1.myworkdayjobs.com

Claims Specialist

ERGO NEXT InsuranceUnited States· 3 mo ago
RemoteFinance$100k–$143k/yrapply on job-boards.greenhouse.io