Jobs · OTHR · Mississippi

Registration Specialist | Emergency Access Services | Full Time | Days

Singing River Health System · Gulfport, MS · 4 days ago
OTHRFull-time
The user wants me to convert this job posting into clean semantic HTML following specific rules. Let me analyze the content and structure it appropriately. First, I need to identify the sections: - About the role / Position Overview (the first paragraph describes the role) - Responsibilities (the detailed duties) - Requirements / Qualifications (education, license, certifications, experience) - Physical Demands - Mental Demands - Special Demands - Possibly Benefits? The posting mentions "If you're looking for purpose, teamwork..." but no explicit benefits listed. - Pay/Schedule: Shift is mentioned (6:00 AM - 4:30 PM) and location. Schedule might be included. Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use
  • for lists,

    for prose. - Do NOT repeat job title as heading (page already shows it). The job title is "Patient Access Services Registration Specialist" but not explicitly stated as a heading in the text? Actually the text says "Position Overview The Patient Access Services Registration Specialist is the first point of contact..." So I should not include a heading for the job title. - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. There's no Job ID here. - 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. The disclaimer is legal boilerplate? It says "DISCLAIMER: This is not necessarily an exhaustive list..." That's typical legal boilerplate, but it's part of the job description. The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. The disclaimer is a standard disclaimer about job description not exhaustive. I think we should remove it as it's boilerplate. Also "Apply now and join our team." is application instruction, remove. - 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. - Output ONLY the HTML fragment — no /, no markdown code fences. Now, let's parse the content: The posting starts with a company description: "At Singing River Health System, caring isn’t just part of the job — it’s in our DNA. Whether we’re saving lives, supporting behind the scenes, or showing up for our community, we bring the energy, heart, and hustle every single day. With pride, passion, and commitment, we will improve health and save lives in our community every day." This is about the company, could be "About the role" or "About the company". The rule says use

    for section headings like "About the role". I'll include an "About the role" section with this prose. Then "Shift (6:00 AM - 4:30 PM) Location: Singing River Gulfport Hospital" - this is schedule and location. Could be part of a "Schedule" section or "Details". Since schedule is mentioned, I can create a "Schedule" section with shift and location. "Job Description Summary Job Description Position Overview" - then the overview paragraph. That's the role description. Then "DISCLAIMER: ..." - remove. Then "Education", "License", "Certifications", "Experience", "Reports To", "Supervises" - these are qualifications/requirements. Could group under "Requirements" or "Qualifications". The rule says use headings like "Requirements", "Qualifications". I'll use "Requirements" as a heading and list them. Then "Physical Demands", "Mental Demands", "Special Demands" - these are specific sections. They have detailed content. Should include them as separate sections. Finally, "If you’re looking for purpose, teamwork, and a place where what you do truly matters, you’ve found it. Let’s do big things together. Apply now and join our team." - this is marketing/closing, remove application instruction. Now, structure: 1. About the role (company description + position overview) 2. Responsibilities (the detailed duties from position overview) 3. Requirements (education, license, certifications, experience, reports to, supervises) 4. Physical Demands 5. Mental Demands 6. Special Demands 7. Schedule (shift and location) But note: The position overview includes both a summary and a list of responsibilities. The text: "The Patient Access Services Registration Specialist is the first point of contact... He/She conducts screening... minimizes medical risk... contributes to the success..." This is a mix of prose and duties. I'll separate: a prose paragraph for overview, then a list for responsibilities. Let's extract responsibilities: - First point of contact, ensure pleasant experience for patients and visitors. - Interview patients/representatives to obtain complete and accurate demographic, financial, and insurance information for billing and collecting patient accounts. - Conduct screening for all insurance pre-certification requirements. - Minimize medical risk to patient and minimize Health System liability by correctly identifying the patient, resolving duplicate medical record numbers, identifying the patient with appropriate identification band. - Provide patient with copy of patient's rights and responsibilities, Health System privacy practices, and proper recording of patient's privacy wishes. - Contribute to success of Revenue Cycle by meeting standards for accuracy and attention to detail in registrations and all assigned tasks. These are clear bullet points. Requirements: - Education: High school diploma or equivalent required; some college preferred. - License: N/A (but we can note "License: None required" or omit? The rule says never emit heading followed by filler like "N/A". So maybe omit License line entirely, or include as "License: Not required". But the posting says "License N/A". I'll include as a list item: "License: Not required" but that's filler. Better to omit the License line entirely since it's N/A. - Certifications: Certified Healthcare Access Associate (CHAA) or Certified Revenue Cycle Representative (CRCR) preferred. Must have de-escalation training completed by end of position orientation (90 days); must have appropriate level of de-escalation training. - Experience: Experience in hospital or physician office setting performing registration and scheduling, insurance verification, and/or customer service preferred. - Reports To: Patient Access Manager - Supervises: None Physical Demands: detailed paragraph. I'll keep as prose or break into list? The rule says use
    • for any list of duties/requirements/benefits, and

      for prose. Physical demands is a paragraph describing demands. Could be a single

      or multiple

      . I'll keep as a

      but it's long. Might break into multiple

      for readability. But the rule says use

      for prose. I'll keep as one

      or split by sentences? I'll keep as one

      with line breaks? HTML doesn't care. I'll output as a single

      with the text. Mental Demands: similar, prose. Special Demands: prose. Schedule: Shift (6:00 AM - 4:30 PM) Location: Singing River Gulfport Hospital. Could be a list or prose. I'll make a "Schedule" section with a

      for shift and location. Now, ensure no duplicate headings. Use

      for each section. Let's write HTML. Note: The company description at the top is not exactly "About the role" but about the company. However, the rule says "About the role" is a heading example. I'll use "About the role" for the company description and position overview combined. Alternatively, could have "About the company" but not in the example list. The example list: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So "About the role" is appropriate. I'll structure:

      About the role

      At Singing River Health System, caring isn’t just part of the job — it’s in our DNA. Whether we’re saving lives, supporting behind the scenes, or showing up for our community, we bring the energy, heart, and hustle every single day. With pride, passion, and commitment, we will improve health and save lives in our community every day.

      The Patient Access Services Registration Specialist is the first point of contact at Singing River Health System and must ensure a pleasant experience for both patients and visitors. The Registration Specialist interviews patients and/or the patient's representative to obtain complete and accurate demographic, financial, and insurance information required for billing and collecting patient accounts. He/She conducts screening for all insurance pre-certification requirements. The Registration Specialist minimizes medical risk to the patient and minimizes Health System liability by correctly identifying the patient, resolving duplicate medical record numbers, identifying the patient with the appropriate identification band, providing the patient with a copy of the patient's rights and responsibilities, and the Health System privacy practices and proper recording of the patient's privacy wishes. He/She contributes to the success of the Revenue Cycle by meeting standards for accuracy and attention to detail in registrations and all assigned tasks.

      But the responsibilities are also listed in that paragraph. I should separate responsibilities into a list under "Responsibilities". The paragraph includes both overview and duties. I'll split: first paragraph is company mission, second paragraph is role overview, then responsibilities as list. Better: "About the role" includes company description and a brief role summary. Then "Responsibilities" lists the duties. Let's do:

      About the role

      At Singing River Health System, caring isn’t just part of the job — it’s in our DNA. Whether we’re saving lives, supporting behind the scenes, or showing up for our community, we bring the energy, heart, and hustle every single day. With pride, passion, and commitment, we will improve health and save lives in our community every day.

      The Patient Access Services Registration Specialist is the first point of contact at Singing River Health System and must ensure a pleasant experience for both patients and visitors.

      Responsibilities

      • Interview patients and/or their representatives to obtain complete and accurate demographic, financial, and insurance information required for billing and collecting patient accounts.
      • Conduct screening for all insurance pre-certification requirements.
      • Minimize medical risk to the patient and minimize Health System liability by correctly identifying the patient, resolving duplicate medical record numbers, and identifying the patient with the appropriate identification band.
      • Provide the patient with a copy of the patient's rights and responsibilities, the Health System privacy practices, and ensure proper recording of the patient's privacy wishes.
      • Contribute to the success of the Revenue Cycle by meeting standards for accuracy and attention to detail in registrations and all assigned tasks.

      Requirements

      • Education: High school diploma or equivalent required; some college preferred.
      • Certifications: Certified Healthcare Access Associate (CHAA) or Certified Revenue Cycle Representative (CRCR) preferred. Must have de-escalation training completed by the end of position orientation (90 days); must have appropriate level of de-escalation training.
      • Experience: Experience in hospital or physician office setting performing registration and scheduling, insurance verification, and/or customer service preferred.
      • Reports to: Patient Access Manager
      • Supervises: None

      Physical Demands

      Work is moderately active: involves sitting with frequent requirements to move about the office, move about the facility, and to travel to another facility within the SRHS service area. Work involves exerting a negligible amount of force frequently to lift, carry, push, pull, or otherwise move

Similar jobs