Casual Pediatric Nurse Practitioner Hospitalist

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections 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. Content: - About Children’s Minnesota (organization description) – could be "About the role"? Actually "About the role" is a heading for role description. The posting includes "Position Summary" and description of duties. So we can have

About the role

with prose summarizing position summary? But we must not repeat job title as heading. We can include "About the role" heading with prose about the role (position summary). Then Responsibilities: list of duties bullet points. - Requirements: includes APRN or PA qualifications: education, license, certification, BLS. Also experience: current/previous experience in inpatient pediatrics as a nurse, nurse practitioner or PA preferred. Also physical demands link (but we should not include navigation? It's a link to view Physical Demands; maybe we can include as part of Requirements? It's a requirement but it's a link; we can include as prose maybe. - Qualifications: maybe overlapping with Requirements. But we can combine? The instruction: prefer few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements (including qualifications, experience, physical demands), Benefits (mentions medical, dental, vision, retirement, fringe benefits, shift differentials), Pay (mentioned: posted salary represents a market competitive range based on salary survey benchmark data...). Schedule: maybe not explicit; there is mention of casual position, but no schedule specifics. So we should not create Schedule section unless posting actually states them. It says "This is a casual position***" but no schedule details. So we omit Schedule. - Benefits: we have mention of medical, dental, vision, retirement, other fringe benefits, shift differentials or premium pay for night/weekend/on-call. That's specific enough to create Benefits section. - Pay: we have description of salary determination. That's specific enough. We must not include boilerplate like EEO, equal opportunity, etc. Remove those. Also remove duplicated lines, cookie/navigation/legal etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific duties bullet points, qualifications, etc. We must not include placeholders like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We need to output only HTML fragment, no /, no markdown. Let's extract sections. About the role: Could use the Position Summary paragraph: "As a casual APP Hospitalist, you will play a crucial role in managing the care of hospitalized patients from admission to discharge. You will work independently and in collaboration with physician hospitalists to provide comprehensive assessments and create medical plans of care. You will gain diverse clinical experiences from covering patients in Acute Care units, the Infant Care Center, and serving as the primary team for a wide array of specialty patients such as endocrinology, eating disorders, gastroenterology, pulmonology, nephrology, infectious disease, cardiology, general surgery, urology, ENT, and psychiatry." We could also include the earlier department overview? That's more about department, not role. Might be considered "About the role"? But we can include as prose maybe under About the role. However we should not repeat job title as heading. It's fine. Responsibilities: bullet list: - Collect and synthesize data from historical information, diagnostic tests, therapeutic interventions, and physical examinations. - Determine diagnoses and appropriate interventions consistent with your scope of practice, experience, board certification, and organizational professional staff policy. - Collaborate closely with hospital sub-specialists, surgical staff, nursing staff, and social workers to create comprehensive treatment plans for patients and their families during their hospital stay. Also maybe the earlier duties about managing care etc. But those are in position summary; we could keep them in About the role. We'll keep responsibilities as those three bullet points. Requirements: include education/license/certification for APRN or PA, experience, physical demands. We need to list as

  • . But there are two tracks (APRN or PA). We could list them as separate items. Let's extract: APRN: - Graduate of an accredited Pediatric Nurse Practitioner Program. - Master’s Degree required; Doctorate preferred. - Current MN RN/APRN License. - Nationally Board Certified as a Pediatric Nurse Practitioner with either the Pediatric Nursing Certification Board (PNCB) or American Nurses Credentialing Center (ANCC) - Current BLS certification. Physician Assistant: - Graduate of an accredited Physician Assistants program. - Master’s degree required; Doctorate preferred. - MN Physician Assistant License. - National Certification required by NCCPA. - Current BLS certification. Experience: - Current/previous experience in inpatient pediatrics as a nurse, nurse practitioner or PA preferred. Physical Demands: link to view Physical Demands. We could include as a requirement: "Please click here to view the Physical Demands". Since it's a link, we can include as

    with ... but we don't have URL. We can just include the text as is. We should not invent URL. We'll just include the sentence as prose maybe. But instruction: Use

    • for any list of duties/requirements/benefits. Physical demands is not a list; it's a single item. Could be a

      . We'll treat as

      . Benefits: list: - medical, dental, vision, retirement, and other fringe benefits. - shift differentials or premium pay for positions that require night, weekend or on-call work. We could also mention that benefits are eligible. Pay: description: - The posted salary represents a market competitive range based on salary survey benchmark data for similar roles in the local or national market. - When determining individual pay rates, we consider a wide range of factors including but not limited to market indicators for the specific role, the skills, education, training, credentials and experience of the candidate, internal equity and organizational needs. We could also mention that salary is market competitive. We should not include boilerplate like "All job offers are contingent upon successful completion of an occupational health assessment, drug screen, background investigation, and compliance with the U.S. Government Form I-9, Employment Eligibility Verification." That's more about hiring process; maybe we could include under Requirements? It's not a requirement per se but a condition. Might be considered part of Requirements? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep that info somewhere. Where to put? Could be under Requirements as a note. But it's not a duty/requirement/benefit; it's a condition of offer. Could be a

      under Requirements or a separate section like "Contingencies". But we only have allowed headings list; we could add a generic

      without heading? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we could also have other headings but better to stick to those. The contingency info could be placed under Requirements as a note. Similarly EEO statement should be removed (boilerplate). So we remove that. Also remove lines like "Find us on Facebook @childrensminnesota or on Twitter and Instagram @childrensmn. cildrensMN.org." That's navigation/social media; remove. Also remove "Children’s Minnesota is proud to be recognized by Modern Healthcare as one of 2023’s Top Diversity Leaders." That's boilerplate? It's an accolade but maybe not required; but it's about organization, not role. Could be considered "About the role"? Might be considered organizational info; but we already have organization description earlier. Might keep as part of About the role? It's not about role. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep that accolade? It's about the organization, not the role. It's substantive about employer. Could be included under About the role? But we already have an overview of Children's Minnesota. Might be okay to keep that as part of the organization description. However the instruction says "Prefer a few substantive sections over many thin ones." So we could include organization description under About the role (maybe as first paragraph). That would be substantive. Thus About the role could include both the organization description and position summary. Let's craft About the role paragraph(s): We can have multiple

      under the heading. We'll include:

      Children’s Minnesota is one of the largest pediatric health systems in the United States and the only health system in Minnesota to provide care exclusively to children, from before birth through young adulthood. An independent and not-for-profit system since 1924, Children’s Minnesota is one system serving kids throughout the Upper Midwest at two free-standing hospitals, nine primary care clinics, multiple specialty clinics and seven rehabilitation sites. As The Kids Experts™ in our region, Children’s Minnesota is regularly ranked by U.S. News & World Report as a top children’s hospital. Children’s Minnesota is proud to be recognized by Modern Healthcare as one of 2023’s Top Diversity Leaders.

      Then second paragraph about position summary. Now Responsibilities as

      • . Requirements: we need to include education/license/cert for both APRN and PA, experience, physical demands note, and contingencies (offer contingent upon...). We could structure as:

        Requirements

        • APRN: Graduate of an accredited Pediatric Nurse Practitioner Program; Master’s Degree required; Doctorate preferred; Current MN RN/APRN License; Nationally Board Certified as a Pediatric Nurse Practitioner (PNCB or ANCC); Current BLS certification.
        • Physician Assistant: Graduate of an accredited Physician Assistants program; Master’s degree required; Doctorate preferred; MN Physician Assistant License; National Certification required by NCCPA; Current BLS certification.
        • Experience: Current/previous experience in inpatient pediatrics as a nurse, nurse practitioner or PA preferred.
        • Physical Demands: Please click here to view the Physical Demands.
        • All job offers are contingent upon successful completion of an occupational health assessment, drug screen, background investigation, and compliance with the U.S. Government Form I-9, Employment Eligibility Verification.
        But we need to ensure we don't lose detail: The APRN bullet includes "Current MN RN/APRN License." and "Nationally Board Certified as a Pediatric Nurse Practitioner with either the Pediatric Nursing Certification Board (PNCB) or American Nurses Credentialing Center (ANCC)". We'll include that. Benefits section:

        Benefits

        • Medical, dental, vision, retirement, and other fringe benefits.
        • Shift differentials or premium pay for positions that require night, weekend or on-call work.
        Pay section:

        Pay

        • The posted salary represents a market competitive range based on salary survey benchmark data for similar roles in the local or national market.
        • Individual pay rates are determined by considering market indicators for the specific role, skills, education, training, credentials and experience of the candidate, internal equity and organizational needs.
        We should not include Schedule section. Now ensure we don't repeat job title as heading. We haven't. Now output only HTML fragment. Let's craft final HTML:

        About the role