HIM Tech II

We need to output HTML fragment with sections: About the role? Actually the posting includes Summary, Job Summary/Purpose, Department Description, Experience/Education/Qualifications, Knowledge/Skills/Abilities, Physical Demands. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include a section only when posting has real specific content. So we need to decide which sections have content. We have: - Summary: "Occasionally JOB SUMMARY/PURPOSE" seems weird but then description: "Responsible for performing specialized clerical and technical functions necessary to organize, maintain and use patient medical records within Samaritan Health Services. Typically specializes in one (1) or more of the record management functions. All staff is expected to demonstrate competency in all functions. Specific assignments may vary from day to day depending on the needs of the department." That's about role/responsibilities. Could map to "About the role" or "Responsibilities". Since we have both About the role and Responsibilities headings available. We can choose one. Probably "About the role" for summary, and "Responsibilities" for duties list. But we don't have a list of duties, just prose. Could put under About the role. - Department Description: describes HIM department. Could be part of About the role or maybe separate "About the role". We'll combine. - Experience/Education/Qualifications: includes required education, experience, etc. That maps to "Requirements" and "Qualifications". We have both headings. We could put under "Requirements" the required items, and "Qualifications" maybe preferred? But we need to avoid thin sections. Could combine into one section "Requirements". But we have both headings available; we can choose to use only one if content fits. The instruction: Prefer a few substantive sections over many thin ones. So maybe use "Requirements" for education/experience, and "Skills" for knowledge/skills/abilities. Physical Demands maybe not a standard heading; we could omit if not matching any of the allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Demands not listed, so we should not create a section for it unless we can map to something else? Probably we should omit Physical Demands as it's not a standard heading and we shouldn't invent headings. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples but we could use others? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings. So Physical Demands should be omitted or maybe integrated into Requirements? But it's not really a requirement. Could be omitted as it's not substantive? But we must preserve ALL substantive information; we cannot drop Physical Demands if it's substantive. However we cannot create a heading not in list? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings. However the examples given are typical sections. I think we can create a heading for Physical Demands if we want, but better to stick to given examples to be safe. However we must preserve all substantive info; we could include Physical Demands under a heading like "Requirements" or "Skills"? Not ideal. Could create a section "Physical Demands" using

  even if not in examples; likely acceptable. But the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use others. I'd include Physical Demands as a section. But we also need to avoid filler like "None specified". In Physical Demands, there is a list of activities with frequencies and then at end "None specified". That seems filler. We should drop the "None specified" line. Also the list includes many items with frequencies; we need to preserve all substantive info. The list is a bit weird: It shows categories like CLIMB - STAIRS LIFT (Floor to Waist: 0"-36") 0 - 20 Lbs etc. It seems like a table but we can represent as

  • each line. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none visible. We need to output only HTML fragment. Let's structure:

    About the role

    Responsible for performing specialized clerical and technical functions necessary to organize, maintain and use patient medical records within Samaritan Health Services. Typically specializes in one (1) or more of the record management functions. All staff is expected to demonstrate competency in all functions. Specific assignments may vary from day to day depending on the needs of the department.

    The Health Information Management (HIM) department manages health information systems and medical records to ensure we meet medical, legal and ethical standards. HIM staff work with Samaritan Health Services patients, staff and providers as well as numerous external entities to maintain the accuracy and completeness of the medical record; provide coded data for evaluation of services and reimbursement; and ensure authorized access to patient medical information in accordance with privacy and confidentiality requirements.

    Requirements

    • High school diploma or equivalent required.
    • One (1) year experience, education or training in an HIM related field required.
    • Experience and/or training in the following required:
      • Medical record standards of practice including, but not limited to access and disclosure of protected health information, information retrieval and medical record completion requirements.
      • Medical terminology.
      • Operating computers, document scanners, electronic medical record programs and other office equipment and software.
    • Health Information Technology or other health care related college course work preferred.

    Skills

    • Knowledge of the importance of confidentiality.
    • Ability to organize, plan and prioritize work, as well as concentrate on a task over a period of time without being distracted.
    • Ability to anticipate, recognize and identify issues.
    • Ability to communicate information verbally and in writing so others will understand.
    • Ability to understand information and ideas presented verbally and in writing.
    • Ability to work as part of a team or on your own.

    Physical Demands

    • CLIMB - STAIRS
    • LIFT (Floor to Waist: 0"-36") 0 - 20 Lbs
    • LIFT (Knee to chest: 24"-54") 0 - 20 Lbs
    • LIFT (Waist to Eye: up to 54") 0 - 20 Lbs
    • CARRY 1-handed, 0 - 20 pounds
    • BEND FORWARD at waist
    • KNEEL (on knees)
    • STAND
    • WALK - LEVEL SURFACE
    • ROTATE TRUNK Standing
    • REACH - Upward
    • PUSH (0-20 pounds force)
    • PULL (0-20 pounds force)
    • SIT
    • CARRY 2-handed, 0 - 20 pounds
    • ROTATE TRUNK Sitting
    • REACH - Forward
    • MANUAL DEXTERITY Hands/wrists
    • FINGER DEXTERITY PINCH Fingers
    • GRASP Hand/Fist
    We omitted "None specified". Also we omitted frequencies (Rarely, Frequently etc.) because they were attached to each? Actually the original had headings: Rarely (1 - 10% of the time) (11 - 33% of the time) Frequently (34 - 66% of the time) Continually (67 - 100% of the time) then list of items. It seems those headings apply to the list? The formatting is weird. It might be that each item has a frequency column missing. Since we cannot infer, we should keep the items as is, but we lost the frequency descriptors. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The frequencies are substantive. We need to include them. However we don't know which frequency applies to which item. The original: PHYSICAL DEMANDS Rarely (1 - 10% of the time) (11 - 33% of the time) Frequently (34 - 66% of the time) Continually (67 - 100% of the time) CLIMB - STAIRS LIFT (Floor to Waist: 0"-36") 0 - 20 Lbs LIFT (Knee to chest: 24"-54") 0 - 20 Lbs LIFT (Waist to Eye: up to 54") 0 - 20 Lbs CARRY 1-handed, 0 - 20 pounds BEND FORWARD at waist KNEEL (on knees) STAND WALK - LEVEL SURFACE ROTATE TRUNK Standing REACH - Upward PUSH (0-20 pounds force) PULL (0-20 pounds force) SIT CARRY 2-handed, 0 - 20 pounds ROTATE TRUNK Sitting REACH - Forward MANUAL DEXTERITY Hands/wrists FINGER DEXTERITY PINCH Fingers GRASP Hand/Fist None specified It seems the frequencies headings are just labels but not aligned. Probably the intent is to show that each activity has a frequency classification (Rarely, Frequently, etc.) but the formatting got messed. Since we cannot determine mapping, we could preserve the headings as a preamble and then list items. We could include a

    that says the frequency categories: Rarely (1-10% of the time), (11-33% of the time), Frequently (34-66% of the time), Continually (67-100% of the time). Then list items without frequencies. That preserves the info. Thus:

    Physical Demands

    Frequency categories: Rarely (1 - 10% of the time), (11 - 33% of the time), Frequently (34 - 66% of the time), Continually (67 - 100% of the time).

    • CLIMB - STAIRS
    • LIFT (Floor to Waist: 0"-36") 0 - 20 Lbs
    • LIFT (Knee to chest