Jobs · Healthcare · Florida

RN - Specialty II - PACU - FT - 3rd Shift - MRH

Memorial Healthcare System · Hollywood, FL · 1 mo ago
HealthcareFull-time
We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Given content: Location: Hollywood, Florida (maybe we can include as a short p? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So location can be a short p. Then we have a paragraph about reputation etc. That's prose. Then "Learn more below." maybe ignore. Then "Summary Provides direct patient care..." That's a summary; could be placed under About the role? Or maybe we treat as About the role section. Responsibilities: list of bullet points (the responsibilities paragraph is a long sentence with many items separated by periods). We need to convert to

  • . The responsibilities text: "Evaluates learning needs of the patient and, or family and provides patient and family education appropriate to age, culture, condition, and circumstances.Plans, implements, and evaluates patient care based on patient assessment to optimize outcomes and maximize available resources. Monitors, documents, and communicates patient condition as appropriate.Effectively delegates patient care to ancillary personnel. May precept student nurses and new hires.Collaborates as needed across disciplines to coordinate patient care, including disposition, referral, and spiritual and, or psychosocial support needs.Maintains requirements of Clinical Ladder." We need to split each sentence into li. Competencies: list of competencies in caps separated by commas. That's like a list; we can put under Skills or Competencies. The instruction: Use h3 for section headings like Skills. So we can have Skills section with ul li of each competency. Education And Certification Requirements: list of many items. That's Requirements or Qualifications. We'll put under Requirements (or Qualifications). Probably Requirements. Additional Job Information: includes Complexity of Work, Required Work Experience, Other Information (department specific credentials etc). We can include under Requirements or maybe a separate section like Qualifications. We'll keep Requirements. Working Conditions And Physical Requirements: a long list of percentages. This is specific content; we could include under a section like Working Conditions. But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No explicit Working Conditions. Could we put under Requirements? Might be okay but it's not exactly requirements. However instruction: Prefer a few substantive sections over many thin ones. We could incorporate working conditions into Requirements or maybe into a section like Requirements (since it's about job demands). But maybe better to create a section like Requirements and include both education/certification and working conditions as subpoints? However we must not invent headings not in list. So we cannot create a "Working Conditions" heading unless we map to one of allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit everything into those. We could treat "Requirements" as encompassing education, certification, experience, working conditions. "Qualifications" maybe similar; but we can choose to use either Requirements or Qualifications, not both if thin. Let's use Requirements for education/certification/experience/working conditions, and Skills for competencies. About the role for summary/intro. Responsibilities as given. We must not include Benefits, Pay, Schedule unless posting actually states them. It does not mention pay, benefits, schedule. So omit those sections. We also need to include location as short p maybe before sections. We must not repeat job title as heading (not given). No job ID. We must remove boilerplate: EEO, equal opportunity, scam-warning, etc. Also remove disclaimer about job description not exhaustive, wages shown on independent job boards, etc. Also remove Veteran's Preference, accommodation contact, etc. Also remove "Learn more below." and maybe the introductory fluff about reputation? That is substantive? It's about organization reputation; could be part of About the role. We'll keep it as prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all the specifics: e.g., the list of ACLS certifications etc. Must keep them. We need to format as HTML fragment only. Let's craft:

    Location: Hollywood, Florida

    About the role

    [the summary paragraph plus reputation intro? We'll combine.]

    We need to include the reputation paragraph: "We have an outstanding reputation for providing patient- and family-centered care that exceeds all expectations. Together, we have created an award-winning, nationally-recognized system where every effort is focused on delivering exceptional care throughout our communities." plus maybe "Career opportunities exist on diverse teams across our many facilities where you can search open positions and apply online to join #teamMHSflorida." That's more like generic; maybe we can keep but it's not substantive? It's about career opportunities; could be considered part of About the role. We'll keep it. Then the Summary: "Provides direct patient care in a designated specialty unit in accordance with applicable scope and standards of practice and with the policies, values, and mission of the organization." We'll combine into one or two p tags. Responsibilities: h3 Responsibilities then ul li each sentence. We need to split sentences correctly. Let's list them: 1. Evaluates learning needs of the patient and, or family and provides patient and family education appropriate to age, culture, condition, and circumstances. 2. Plans, implements, and evaluates patient care based on patient assessment to optimize outcomes and maximize available resources. 3. Monitors, documents, and communicates patient condition as appropriate. 4. Effectively delegates patient care to ancillary personnel. 5. May precept student nurses and new hires. 6. Collaborates as needed across disciplines to coordinate patient care, including disposition, referral, and spiritual and, or psychosocial support needs. 7. Maintains requirements of Clinical Ladder. Note there is a missing period after "circumstances." Actually text: "Evaluates learning needs of the patient and, or family and provides patient and family education appropriate to age, culture, condition, and circumstances.Plans, implements, and evaluates patient care based on patient assessment to optimize outcomes and maximize available resources." There's no space after period before "Plans". We'll still treat as separate. Now Skills: h3 Skills then ul li each competency. Competencies list: ACCOUNTABILITY, CUSTOMER SERVICE, DEVELOPMENT AND IMPLEMENTATION OF PLAN OF CARE, KNOWLEDGE OF DISEASE PROCESS, ORGANIZATION SKILLS (4), PATIENT AND FAMILY CENTERED CARE, PATIENT SAFETY - NURSING, PROBLEM SOLVING - PATIENT CARE, RESPONDING TO CHANGE, STANDARDS OF BEHAVIOR We need to keep exactly as given, maybe preserve parentheses. Now Requirements: h3 Requirements then we need to include education and certification requirements, additional job information (complexity of work, required work experience, other information), and working conditions. We need to preserve all details, not summarizing. We'll create a ul li for each bullet? But the content is not naturally bullet; we can still use p paragraphs for prose sections, and ul for lists where appropriate. Education And Certification Requirements: a long list of items each on new line but separated by commas? Actually each item ends with a line break? In the text they are separated by line breaks? They appear as: Accredited Program: Nursing (Required) ACLS American Heart E-Card (ACLS AHA ECARD) - American Heart Association (AMERICAN HEART), ACLS American Heart RQI E-Card (ACLS AHA-RQI ECARD) - American Heart Association (AMERICAN HEART), ACLS Certification_non ecard (ACLS AHA) - American Heart Association (AMERICAN HEART), ACLS Certification (ACLS RC) - Red Cross (RED CROSS), ACLS Certification Grace (ACLS GRACE) - Employee Grace Period for Essential Credential (GRACE), BLS American Heart E-Card (BLS AHA ECARD) - American Heart Association (AMERICAN HEART), BLS American Heart RQI E-Card (BLS AHA-RQI ECARD) - American Heart Association (AMERICAN HEART), BLS Cert American Heart_non ecard (BLS AHA) - American Heart Association (AMERICAN HEART), BLS Certification Grace (BLS GRACE) - Employee Grace Period for Essential Credential (GRACE), BLS Cert Red Cross (BLS RC) - Red Cross (RED CROSS), Registered Nurse Compact License (RN LICENSE COMPACT) - Compact RN Multistate, Registered Nurse License (RN LICENSE) - State of Florida (FL) We could treat each line as a li? But many items are comma-separated within a line. Better to keep as a p with the list as is, preserving commas. However instruction: Use
    • for any list of duties/requirements/benefits. This is a list of requirements; we should use ul li. We can split each distinct requirement item separated by commas? But that would be messy and might lose nuance. However we can treat each line before a comma as separate? The text uses commas to separate items, but also includes parentheses and hyphens. Might be okay to split by commas but some items have commas inside parentheses (e.g., "ACLS American Heart E-Card (ACLS AHA ECARD) - American Heart Association (AMERICAN HEART)" includes no internal commas besides separating items. Actually there is a comma after the closing parenthesis before "- American Heart Association". So splitting by commas would break that incorrectly. Thus maybe better to keep as a p and not use ul for that section, but instruction says use ul for any list of duties/requirements/benefits. However we could argue that the list is not a simple list but a detailed description; still it's a list. But to be safe, we could use ul li where each line break is a separate item (the lines as presented). The original text shows each certification on its own line? Actually they are separated by line breaks in the source? The given text shows line breaks after each item? Let's examine: "Accredited Program: Nursing (Required)ACLS American Heart E-Card (ACLS AHA ECARD) - American Heart Association (AMERICAN HEART), ACLS American Heart RQI E-Card (ACLS AHA-RQI ECARD) - American Heart Association (AMERICAN HEART), ACLS Certification_non ecard (ACLS AHA) - American Heart Association (AMERICAN HEART), ACLS Certification (ACLS RC) - Red Cross (RED CROSS), ACLS Certification Grace (ACLS GRACE) - Employee Grace Period for Essential Credential (GRACE), BLS American Heart E-Card (BLS AHA ECARD) - American Heart Association (AMERICAN HEART), BLS American Heart RQI E-Card (BLS AHA-RQI ECARD) - American Heart Association (AMERICAN HEART), BLS Cert American Heart_non ecard (BLS AHA) - American Heart Association (AMERICAN HEART), BLS Certification Grace (BLS GRACE) - Employee Grace Period for Essential Credential (GRACE), BLS Cert Red Cross (BLS RC) - Red Cross (RED CROSS), Registered Nurse Compact License (RN LICENSE COMPACT) - Compact RN Multistate, Registered Nurse License (RN LICENSE) - State of Florida (FL)" It seems there is no line break after the first item; it's all one paragraph with commas separating items. So it's a comma-separated list. Using ul li would be awkward. Given the instruction to use ul for any

Similar jobs