Non Clinical Case Manager

,

,

• . No CSS classes, no inline styles, no
  , no
  . Must preserve all original content word-for-word, no addition, removal, summarizing, rephrasing. Must convert the given raw text (which already contains some HTML tags like

  , ,

  ,
  • ,
    , etc.) into the required format: use

    for paragraphs,

    for section headers,

    • for list items. Must preserve content exactly, but we need to strip out any tags not allowed (,
      , style attributes, etc.) and replace with appropriate tags. We must not add or remove content; we must keep the text exactly as is, but we can change markup. So we need to extract the plain text content (including spaces, line breaks?) and then wrap in appropriate tags. We must not add any extra text. Must not summarize. Must preserve all original content word-for-word. That means we cannot omit any words, punctuation, etc. We must keep the same sequence of characters (except we can change tags). So we need to produce HTML where the text nodes are exactly the original text (including spaces, line breaks?). The original text includes many

      tags with empty content, tags,
      tags, style attributes, etc. We need to strip those and produce only allowed tags. We must not add any extra whitespace that changes the content? Probably okay as long as the visible text is same. But we must be careful. Let's extract the plain text from the given input, preserving order. Input:

      We provide meaningful careers that connect people with purpose.

      We are united by a common purpose of providing the best and safest care; and by our shared values of Care, Truth, Participation, Compassion and Dignity.

      Netcare invites you to be part of our journey.

      ROLE SUMMARY
      
      The Non-Clinical Case Manager mitigates financial risk by providing justification of the hospitalisation, encompassing level of care and length of stay to fund administrators.
      Non-Clinical Case Managers work collaboratively with clinical coders to provide complete clinical coding of the hospital event. The incumbent will be responsible for liaising between the patients, treating clinicians and managed care organisations to provide an accurate clinical motivation/indication of the patient’s stay in hospital. The Non-Clinical Case Manager is an integral part of a team, alleviating the administrative burden of the Case Manager which have a similar, but clinical focus. The Non-Clinical Case Manager works with the billings manager to achieve the billing cluster KPIs.

      KEY WORK OUTPUT AND ACCOUNTABILITIES

      DISRUPTIVE INNOVATION

      Case Management

      • Systematic application of knowledge to ensure complete case management of a patient’s event in terms of LOS, LOC and medical aid benefits.
      • Provide electronic data to substantiate length of stay and level of care for patient’s stay in hospital.
      • Ensure correct clinical coding for all patients as per clinical coding SOP.
      • Apply knowledge to ensuring that materials and services are correctly classified on the system.
      • Escalation of case management trends to the BOC Billings Manager for discussion in funder operational meetings.
      • Monitoring the patients in progress report and ensuring that patients ward movements, bed status and level of care on the system is accurate.
      • Facilitate discharge planning and movement of patients to step-down or rehab facilities.
      • Efficient management of e-queries as allocated on Debtpack.
      • Assist with any other duties assigned by the BOC and Billings Manager from time to time.
      • Apply acquired case manager knowledge for the resolution of rejections of patient accounts in terms of LOS and LOC.

      Diagnostic and procedural coding

      • Ensure appropriate, complete, and relevant diagnostic and procedural coding of all patient records within the cluster while the patient is in progress.
      • Make use of Health Code Index.

      Build and maintain stakeholder relationships

      • Liaise with a network of internal and external stakeholders to ensure final billing.
      • Develop collaborative relationships to help accomplish work goals.

      Effective communication

      • Effective communication to medical schemes by utilising the rules of engagement published in the Netcare Tariff and Billing Guidelines.
      • Effective communication, collaboration and consultation with other role players in the healthcare team.

      Legal compliance

      • Compliance with all industry relevant legislative acts, regulations and circulars.
      • Compliance with Group Policies, Procedures and Processes.

      TRANSFORMATION OF OUR SOCIET

      Training and development

      • Identify own training needs and communicate with line manager.
      • Formal coding training via Insight platform is compulsory.
      • Onboarding Non-Clinical Case Manager Insight training is compulsory.

      Teamwork

      • Actively participate as a member of a team to achieve daily goals, so that work allocation is not carried over to the next day.

      Personal and professional development

      • Active involvement in own professional development to maintain a satisfactory level of skill and knowledge.
      • Keep up to date with Netcare’s evolving policies and procedures.

      SKILLS PROFILE

      EDUCATION

      Required

      • DUXAH Non-clinical Case Manager qualification or equivalent.

      WORK EXPERIENCE

      Required

      • 1 year hospital internship either before or after successful completion of Non-clinical Case Manager qualification.
      • General administrative skills.
      • Computer literate.

      KNOWLEDGE

      Required

      • Understanding of a patients journey in the private healthcare environment from patient admission to final billing.

      PHYSICAL REQUIREMENTS

      • In the event of any physical or psychological limitation that may impair the employee’s ability to perform the required job function, the employee must consult the employer for reasonable accommodation.

      SKILLS

      Customer Focus and Service Delivery

      • The capacity to identify and respond to the needs of *internal and external customers.

      Personal Work Ethic

      • Capacity to instil an ethic of quality and consistency in self and others.

      Building Relationships

      • Capacity to establish constructive and effective relationships.

      Communication

      • The capacity to clearly present information, either written or verbal.

      Teamwork

      • Capacity to cooperate with others to work towards a common goal.

      Technical Knowledge

      • The capacity to perform a technical function to required standards.

      WORKING CONDITIONS

      • Professional flexibility in working hours while supporting daily business operations which may include weekends and night shifts where applicable.
      • Will interact with internal and external customers through several different means.

      NETCARE VALUES AND BEHAVIOURS

      Netcare Values
      At Netcare, our core value is care. We care about the dignity of our patients and all members of the Netcare family. We care about the participation of our people and our partners in everything we do. We care about truth in all our actions. We are passionate about quality care and professional excellence.

      • At Netcare, our core value is care.
      • We care about the dignity of our patients and all members of the Netcare family.
      • We care about the participation of our people and our healthcare partners in everything that we do.
      • We care about the truth in all our actions.
      • We listen with empathy and respond with acts of compassion in all interactions with our patients and their families.

      
      The Netcare Way

      Netcare is committed to providing quality care. Our basic service standard holds us accountable for the below seven behaviours which you will be accountable to uphold:

      • Respect - I always greet everyone to show my respect.
      • Identity - I always wear my name badge to show my identity.
      • Dignity - I always treat others with consideration and humility to uphold dignity
      • Care - I always act in the best interest of Netcare and others to show I care
      • Compassion - I always listen with empathy and respond with kind action to show my compassion
      • Appreciation - I always say thank you to show my appreciation.
      • Diversity- I always embrace diversity to strengthen inclusivity and belonging.

      Join the team committed to providing the best and safest health and care.

      We need to produce HTML with

      for paragraphs,

      for section headers (like "ROLE SUMMARY", "KEY WORK OUTPUT AND ACCOUNTABILITIES", "Case Management", etc). The original uses for headings. We need to convert those to

      . Also need to treat list items: they are already in

      • . We must keep them but ensure no extra tags like inside li? The rules: Use
        • for list items. It didn't forbid having inside li? It says use
          • for list items (duties, requirements, qualifications, skills). It didn't say we cannot have other tags inside li, but we should preserve content word-for-word, which includes tags inside some list items (e.g., in Netcare Values list). We must preserve those tags? The instruction: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That includes the tags inside the list items. However earlier we said we must remove all tags not allowed (,
            , style attributes). But that conflicts with preserving content word-for-word. The instruction says preserve original content word-for-word, but also says use only certain tags. Likely they mean preserve the textual content, not the markup. So we should strip out all original markup and reapply our own tags, but keep the text exactly as it appears (including any bolded words? The bold is markup, not text. If we strip , we lose the bold formatting but the text remains. The instruction "Preserve ALL original content word-for-word" likely refers to the textual content, not the HTML tags. So we can drop ,
            , style attributes, etc. We must not add any extra words or remove any words. So we need to output the same plain text, just wrapped in allowed tags. Thus we need to extract plain text from the input, preserving spaces and line breaks as they appear (but we can normalize line breaks? Probably we should keep them as they appear in the original text nodes). However converting to HTML will treat line breaks as whitespace; we can just output paragraphs. Simplify: We'll produce a series of

            blocks for paragraphs, and

            for headings. We need to identify headings: "ROLE SUMMARY", "KEY WORK OUTPUT AND ACCOUNTABILITIES", "DISRUPTIVE INNOVATION", "Case Management", "Diagnostic and procedural coding", "Build and maintain stakeholder relationships", "Effective communication", "Legal compliance", "TRANSFORMATION OF OUR SOCIET", "Training and development", "Teamwork", "Personal and professional development", "SKILLS PROFILE", "EDUCATION", "WORK EXPERIENCE", "KNOWLEDGE", "PHYSICAL REQUIREMENTS", "SKILLS", "Customer Focus and Service Delivery", "Personal Work Ethic", "Building Relationships", "Communication", "Teamwork", "Technical Knowledge", "WORKING CONDITIONS", "NETCARE VALUES AND BEHAVIOURS", "Netcare Values", "The Netcare Way". Also there is "Join the team committed to providing the best and safest health and care." at end. But many of these are already within tags. We'll treat each block as a heading (

            ) unless it's part of a paragraph? For example early bold sentences: "We provide meaningful careers that connect people with purpose." etc. Those are not headings but introductory paragraphs. Should they be

            ? Yes. Thus we need to parse the input sequentially, but easier: we can just output the whole thing as a series of

            tags, except where we see a line that is all caps or ends with colon? But spec says use

            for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we should only use

            for those specific section headers. However the input includes many headings like "Case Management", "Diagnostic and procedural coding", etc. Those are section headers within the job description. So we should convert them to

            . Also "KEY WORK OUTPUT AND ACCOUNTABILITIES" is a heading. "DISRUPTIVE INNOVATION" maybe a heading. "TRANSFORMATION OF OUR SOCIET" heading. "Training and development", "Teamwork", "Personal and professional development", "SKILLS PROFILE", "EDUCATION", "WORK EXPERIENCE", "KNOWLEDGE", "PHYSICAL REQUIREMENTS", "SKILLS", "Customer Focus and Service Delivery", "Personal Work Ethic", "Building Relationships", "Communication", "Teamwork", "Technical Knowledge", "WORKING CONDITIONS", "NETCARE VALUES AND BEHAVIOURS", "Netcare Values", "The Netcare Way". Also "ROLE SUMMARY". Also maybe "Join the team..." is a paragraph. Thus we will convert each block that stands alone (not part of a sentence) to

            . However some blocks are inside paragraphs like "We provide meaningful careers..." which is a sentence; we should keep as

            with the text (no ). Similarly "We are united by a common purpose..." etc. Also there are tags inside list items (like care). Those should be kept as plain text? The instruction to preserve content word-for-word suggests we should keep the word "care" but not the tags. So we will output just "care". Similarly for other bolded words inside list items. Thus we need to strip all ,
            , , style attributes, etc., and output plain text. Let's extract the plain text sequentially. I'll manually copy the text, removing tags. Start:

            We provide meaningful careers that connect people with purpose.

            => "We provide meaningful careers that connect people with purpose."

            => empty

            We are united by a common purpose of providing the best and safest care; and by our shared values of Care, Truth, Participation, Compassion and Dignity.

            => "We are united by a common purpose of providing the best and safest care; and by our shared values of Care, Truth, Participation, Compassion and Dignity."

            Netcare invites you to be part of our journey.

            => "Netcare invites you to be part of our journey."

            Then "ROLE SUMMARY
            
            " => text: "ROLE SUMMARY" followed by two line breaks. Then the paragraph: "The Non-Clinical Case Manager mitigates financial risk by providing justification of the hospitalisation, encompassing level of care and length of stay to fund administrators. Non-Clinical Case Managers work collaboratively with clinical coders to provide complete clinical coding of the hospital event. The incumbent will be responsible for