Care Coordinator - Documentation Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes "About SonderMind" and "About The Role". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. We have: - About SonderMind (company description). Could be a section maybe "About SonderMind". Not listed in examples but we can use heading "About SonderMind"? The examples list "About the role" etc. But we can still use

for any section heading; they gave examples but not exclusive. Probably we should include "About SonderMind" as a section. - About The Role: description of role. Could be "About the role". Use

About the role

. - Responsibilities: "What You’ll Do" bullet list. That's responsibilities. Use

Responsibilities

with

• items. - Success metrics / performance measurement: "What does success look like?" and "How Performance Is Measured". Could be "Performance Expectations" or "Success Metrics". Might be considered part of responsibilities or qualifications? But we can create a section "Success Metrics" maybe. However instruction: prefer few substantive sections over many thin ones. Could combine success metrics into responsibilities? But they are distinct. Might be okay to have a section "Performance Expectations". However they didn't list that as example but it's okay. - Who You Are: Experience, Compliance Knowledge, System Aptitude, Communication Skills, Attention to Detail & Time Management. That's qualifications/requirements. Could be "Requirements" or "Qualifications". Use

  Requirements

  with list. - Benefits: "Our Benefits" includes hourly rate and list of benefits. That's Benefits and Pay. The posting states hourly rate $21.64 per hour non-negotiable. So we should include Pay and Benefits sections. According to instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state hourly rate and benefits list. So we can have

  Pay

  with paragraph stating hourly rate. And

  Benefits

  with list. - Schedule: The posting includes schedule: "This a full-time opportunity, and the schedule is Monday-Friday, 9:00am-5:30pm PST (10:00am–6:30pm MST / 11:00am-7:30pm CST /12:00pm–8:30pm EST)." So we should include Schedule section. - Other sections like "Application Deadline", "Our Hiring Process & Use of AI", "Equal Opportunity" are boilerplate to remove. Thus final HTML: sections: About SonderMind, About the role, Responsibilities, Requirements, Pay, Benefits, Schedule. Possibly also "Performance Expectations"? But we might incorporate success metrics into Responsibilities or Requirements? The success metrics are about what success looks like and how performance measured. Could be its own section "Performance Expectations". However instruction: prefer few substantive sections over many thin ones. Adding another section may be okay if it's substantive. It is substantive. But we could also fold into Responsibilities? Might be better to keep separate as "Performance Expectations". Let's see if we can keep sections: About SonderMind, About the role, Responsibilities, Requirements, Pay, Benefits, Schedule. That's 7 sections. If we add Performance Expectations, 8. Might be okay but instruction says prefer few substantive sections over many thin ones. These are all substantive. I'd keep 7. Now we need to output only HTML fragment, no /, no markdown fences. We need to use

  for headings,

  for prose,

  • for lists. We must preserve all substantive information. Ensure we don't lose details. Let's extract content. About SonderMind paragraph: "At SonderMind, we believe everyone deserves one personalized, connected, and effective mental health destination to take care of their mental health and well-being at any stage of life. SonderMind care encompasses everything from therapy and medication management to meditation and mindfulness exercises. Our clinicians leverage our digital tools and research to deliver increasingly high-quality care and to develop thriving practices. Combining technology and human connection, SonderMind drives better outcomes through our comprehensive approach. Learn more about SonderMind at sondermind.com or download the mobile app, available on iOS and Android. To follow the latest SonderMind news, get to know our clients, and learn about what it’s like to work at SonderMind, you can follow us on Instagram, Linkedin, and Twitter. Additionally, we expect all team members to effectively leverage modern AI technologies as part of their everyday workflow, and to continuously adapt as new tools emerge. Familiarity with job-relevant AI platforms such as Gemini, ChatGPT, Claude, GitHub Copilot or other industry-standard AI productivity tools is expected and considered essential for success at this company." We keep all that. About The Role: "As a Documentation Specialist, you will serve as the operational backbone of our clinical compliance and provider support workflows. In this role, you will be directly responsible for managing clinical information flow, conducting daily chart audits, and partnering closely with behavioral health providers (therapists and psychiatric nurse practitioners) to ensure all required documentation meets strict payer and regulatory compliance standards. This is a fast-paced, highly detail-oriented administrative role where you will manage active caseloads across multiple Electronic Health Record (EHR) and payer portal systems. You will act as the go-to subject matter expert for clinicians on documentation timelines, safety plan execution, and chart completion, directly protecting patient care continuity and billing revenue integrity. This a full-time opportunity, and the schedule is Monday-Friday, 9:00am-5:30pm PST (10:00am–6:30pm MST / 11:00am-7:30pm CST /12:00pm–8:30pm EST)." Note schedule appears here; we will later put schedule in its own section, but we need to avoid duplication. We'll remove schedule sentence from About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we remove schedule from About the role, we lose that info unless we put it in Schedule section. So we should keep schedule info in Schedule section, and we can omit it from About the role to avoid duplication. However we must preserve all substantive information; moving it to another section is fine as long as it's present somewhere. So we can edit About the role to exclude the schedule sentence. Let's check if any other schedule mention elsewhere? No. Thus About the role paragraph without schedule sentence. Now Responsibilities: "What You’ll Do" list items. We need to capture each bullet. List: - Session Note & Record Management: Accurately download initial evaluation notes, clinical reviews, and treatment plans from external payer portals and upload/attach them into our EHR system, ensuring seamless and error-free record integration. - Outstanding Documentation Tracking & Compliance Enforcement: Daily monitor, audit, and follow up on outstanding clinical documentation across assigned provider caseloads to ensure strict adherence to non-negotiable compliance requirements. - Provider Partnership & Communication: Serve as the dedicated point of contact for clinicians regarding documentation procedures, template orientation, chart addendums, and clinical review workflows, providing prompt, professional, and supportive guidance via email and internal messaging. - Documentation Log Maintenance & Quality Assurance: Maintain meticulous, real-time tracking logs of all documentation statuses, upholding data integrity and strict HIPAA compliance at all times. - New Provider Onboarding Support: Assist leadership with clinical onboarding by guiding newly hired clinicians through documentation expectations, EHR charting workflows, and compliance milestones during their initial ramp-up. - Payer & Administrative Liaison: Coordinate documentation exchanges between clinicians and insurance liaisons to resolve chart discrepancies and fulfill audit requests. - Workflow Optimization & Trend Reporting: Track recurring charting bottlenecks or non-compliance trends, providing actionable feedback to operations leadership to streamline daily workflows and enhance team efficiency. - Other responsibilities and ad-hoc projects from time to time based on business needs. We'll put each as
  • . Now Requirements / Who You Are: We need to capture each bullet. List: - Experience: 1–2+ years of administrative, care coordination, or operational experience in a healthcare or behavioral health setting. - Compliance Knowledge: Strong working knowledge of clinical documentation standards, medical records management, and strict adherence to HIPAA regulations (preferred) - System Aptitude: Proven proficiency navigating Electronic Health Record (EHR) platforms and administrative tracking systems (experience with Google Workspace, Microsoft Excel, and web-based portals). - Communication Skills: Excellent written and verbal communication skills with the ability to convey compliance requirements to clinicians in a warm, collaborative, and professional manner. - Attention to Detail & Time Management: High attention to detail with the ability to prioritize a high daily volume of tasks, manage competing deadlines, and maintain focus in a fully remote environment. We could format as list items. Now Pay: "Our Benefits The hourly rate for this role is $21.64 per hour and is non-negotiable." Actually that sentence is under "Our Benefits". We'll extract Pay: hourly rate $21.64 per hour non-negotiable. Now Benefits: list of benefits after that sentence. Benefits list: - A generous PTO policy, with a minimum of three weeks off per year - A holiday schedule that follows standard U.S. holidays - Free therapy coverage benefits to ensure employees have access to the care they need (must be enrolled in a qualifying medical plan to participate) - Competitive Medical, Dental, and Vision coverage, with plans to meet every need — including HSA (with $1,100 company contribution) and FSA options - Employer-paid short-term disability, long-term disability, life & AD&D, plus coverage of the salary difference for up to seven weeks of short-term disability leave (after the required waiting period) - Eight weeks of paid Parental Leave; if the parent also qualifies for STD, this benefit is in addition, allowing for 8–16 weeks of paid leave - 401(k) retirement plan with 100% match on up to 4% of base salary, immediately vested - Join teammates from across the country at our annual company gathering - Company shutdown between Christmas and New Year’s - Supplemental life insurance, pet insurance, commuter benefits, and more We'll put each as
  • . Now Schedule: schedule sentence: "This a full-time opportunity, and the schedule is Monday-Friday, 9:00am-5:30pm PST (10:00am–6:30pm MST / 11:00am-7:30pm CST /12:00pm–8:30pm EST)." Note there is a typo "This a". We'll keep as is. We'll put in

    . Now we need to ensure we didn't include any boilerplate like "Application Deadline", "Our Hiring Process & Use of AI", "Equal Opportunity". Remove them. Now produce HTML. Structure