Patient Service Coordinator
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings only if they exist. The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when appropriate. But we need to include a section only when posting has real, specific content for it. We should not repeat job title as heading. Also we should not put Job ID etc.
We need to decide which sections to include: About the role (maybe corresponds to Position Summary?), Responsibilities (maybe from Position Summary?), Requirements (Education, Experience, License/Certification?), Qualifications (maybe Knowledge/Skills/Abilities?), Skills (maybe part of Knowledge/Skills/Abilities?), Benefits, Pay, Schedule.
We have content: About Children’s Minnesota (organization overview) - could be "About the role"? Actually About the role is about the job, not the organization. But we could treat "About Children’s Minnesota" as "About the role"? Might be misaligned. However instructions say use those headings as examples; we can use other headings if appropriate? 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. Probably we should map content to those headings.
Let's extract:
- About the role: Could be Position Summary (description of PSC role). Also maybe Department Overview? But Position Summary is more about role.
- Responsibilities: Could be duties from Position Summary: providing customer service, registration, obtaining info, supporting patient care, administrative support, technology resource.
- Requirements: Education (high school diploma or equivalent, post secondary preferred), Experience (1 year customer service required, 1 year medical office preferred, knowledge of medical insurance preferred), License/Certification/Registration required? No.
- Qualifications: Could be Knowledge/Skills/Abilities list.
- Skills: Could be subset of Knowledge/Skills/Abilities (customer service skills, computer skills, communication, teamwork, HIPAA, problem solving, multitasking). Might duplicate.
- Benefits: "In addition to your salary, this position may be eligible for medical, dental, vision, retirement, and other fringe benefits. Positions that require night, weekend or on-call work may be eligible for shift differentials or premium pay."
- Pay: "The posted salary represents a market competitive range based on salary survey benchmark data for similar roles in the local or national market. Annual salaries displayed are based on full-time employment (40 standard hrs per week). Annual salaries for part-time positions will be prorated based on the employee’s scheduled weekly hours in relation to the full-time standard. When determining individual pay rates, we carefully 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."
- Schedule: Not explicitly given. There's mention of night, weekend or on-call work may be eligible for shift differentials. But no specific schedule. So we should not create Schedule section unless posting actually states them. It does not state schedule, so omit.
Physical Demands: Not in the list of headings; we could either omit or maybe include as a section with a different heading? The instruction says use those headings for section headings; but we could also include other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Probably we should stick to those headings and omit Physical Demands if not covered. However we must preserve ALL substantive information; we cannot drop Physical Demands if it's substantive. But we could incorporate it into another section like Requirements or Qualifications? It's a separate aspect. Could we create a section with heading "Physical Demands"? The instruction didn't forbid other headings, just gave examples. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use h3 for any section headings, and those are examples. So we can use other headings as needed, but must be h3. So we can include Physical Demands as its own h3.
Similarly, we have Department Overview and About Children’s Minnesota (organization info). Could be included as "About the organization" but not in examples. Could be part of "About the role"? Might be okay to include as a separate section like "About Children’s Minnesota". The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. Probably we should map content to those headings.
Let's extract:
- About the role: Could be Position Summary (description of PSC role). Also maybe Department Overview? But Position Summary is more about role.
- Responsibilities: Could be duties from Position Summary: providing customer service, registration, obtaining info, supporting patient care, administrative support, technology resource.
- Requirements: Education (high school diploma or equivalent, post secondary preferred), Experience (1 year customer service required, 1 year medical office preferred, knowledge of medical insurance preferred), License/Certification/Registration required? No.
- Qualifications: Could be Knowledge/Skills/Abilities list.
- Skills: Could be subset of Knowledge/Skills/Abilities (customer service skills, computer skills, communication, teamwork, HIPAA, problem solving, multitasking). Might duplicate.
- Benefits: "In addition to your salary, this position may be eligible for medical, dental, vision, retirement, and other fringe benefits. Positions that require night, weekend or on-call work may be eligible for shift differentials or premium pay."
- Pay: "The posted salary represents a market competitive range based on salary survey benchmark data for similar roles in the local or national market. Annual salaries displayed are based on full-time employment (40 standard hrs per week). Annual salaries for part-time positions will be prorated based on the employee’s scheduled weekly hours in relation to the full-time standard. When determining individual pay rates, we carefully 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."
- Schedule: Not explicitly given. There's mention of night, weekend or on-call work may be eligible for shift differentials. But no specific schedule. So we should not create Schedule section unless posting actually states them. It does not state schedule, so omit.
Physical Demands: Not in the list of headings; we could either omit or maybe include as a section with a different heading? The instruction says use those headings for section headings; but we could also include other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Probably we should stick to those headings and omit Physical Demands if not covered. However we must preserve ALL substantive information; we cannot drop Physical Demands if it's substantive. But we could incorporate it into another section like Requirements or Qualifications? It's a separate aspect. Could we create a section with heading "Physical Demands"? The instruction didn't forbid other headings, just gave examples. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use h3 for any section headings, and those are examples. So we can use other headings as needed, but must be h3. So we can include Physical Demands as its own h3.
Similarly, we have Department Overview and About Children’s Minnesota (organization info). Could be included as "About the organization" but not in examples. Could be part of "About the role"? Might be okay to include as a separate section like "About Children’s Minnesota". The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use h3 for any section headings, and those are examples. So we can use other headings as needed, but must be h3. So we can include Physical Demands as its own h3. Similarly, we have Department Overview and About Children’s Minnesota (organization info). Could be included as "About the organization" but not in examples. Could be part of "About the role"? Might be okay to include as a separate section like "About Children’s Minnesota". The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid other headings. Thus we can include sections: About Children’s Minnesota, Department Overview, About the role (Position Summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Physical Demands. We must use
- for any list of duties/requirements/benefits, and
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to remove EEO statement at end (the long equal opportunity paragraph). Also remove "Please click here to view the Physical Demands" maybe? Actually that is a link; we should keep the Physical Demands info? The posting says "Physical Demands Please click here to view the Physical Demands". No actual details given; just a link. So there is no substantive content; we should not include Physical Demands section if no detail. Since it's just a link, we should drop it. So we omit Physical Demands. Similarly, "The posted salary represents a market competitive range..." is substantive about pay; we keep. Benefits: we have sentence about medical, dental, vision, retirement, other fringe benefits, shift differentials. We also have "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 boilerplate? Might be considered legal/condition; but it's substantive about hiring contingency. Could be considered boilerplate but it's not EEO. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal contingency; maybe we should remove? It's not exactly cookie/navigation, but it's legal. Might be considered boilerplate. Safer to remove? The instruction says remove legal boilerplate. So we should drop that sentence. Also remove "Children’s Minnesota is proud to be recognized by Modern Healthcare as one of 2023’s Top Diversity Leaders." That's accolades; could be kept as part of About Children’s Minnesota? It's substantive about organization. Keep. Also remove social media links? "Find us on Facebook @childrensminnesota or on Twitter and Instagram @childrensmn. Please visit childrensMN.org." That's maybe navigation/promo; could be considered boilerplate? It's not essential job info. Might be removed. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Social media links could be considered navigation/promo; maybe remove. But it's not explicitly listed; but it's like promotional. Safer to remove. Also remove "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." That's accolades; keep maybe. Now we need to structure. Let's extract substantive content: About Children’s Minnesota: - 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. - 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. The national honor recognizes the top diverse healthcare executives and organizations influencing public policy, care delivery, and promoting diversity, equity and inclusion in their organizations and the industry. Department Overview: - The Psychiatric and Psychological departments provide services on both the Minneapolis and St. Paul campuses, with limited services at Woodwinds in Woodbury and Children's West in Minnetonka. - Specific services include individual and family therapy, psychological assessment, neuropsychological assessment, and psychiatric evaluation and medication management (Available to children who are already patients of Children's mental health, pediatric, or subspecialty clinics.) Position Summary (About the role): - The patient services coordinator (PSC) is a pivotal front-line individual who provides exemplary customer service to families, staff and providers, both in-person and by phone. - They promote a positive patient and family experience by answering questions, warmly, promptly and correctly. - They are responsible for efficient and orderly registration and check-in of patients. - Obtains accurate and complete patient demographic, financial information and required consents. - The PSC supports patient care in the clinics and provides overall administrative support to their clinical area. - The individual is also the clinics technology resource. Responsibilities (maybe same as above? Could split). We'll treat Position Summary as About the role, and Responsibilities as the list of duties. Thus Responsibilities list: - Provides exemplary customer service to families, staff and providers, both in-person and by phone. - Promotes a positive patient and family experience by answering questions warmly, promptly and correctly. - Responsible for efficient and orderly registration and check-in of patients. - Obtains accurate and complete patient demographic, financial information and required consents. - Supports patient care in the clinics and provides overall administrative support to their clinical area. - Acts as the clinics technology resource. Requirements: - Education: High school diploma or equivalent required; post secondary education preferred. - Experience: One year of customer service experience required; one year of medical office setting experience preferred; knowledge of medical insurance preferred. - License/Certification/Registration required? No. Qualifications/Knowledge/Skills/Abilities: - Exceptional customer service skills - Strong computer skills such as Microsoft Word, Excel or hospital technology systems - Communicate and interact in respectful and professional manner - Contribute to positive clinic team work environment - Ability to perform front desk clinic functions - HIPAA knowledge and ability to handle confidential information - Demonstrate prompt and reliable attendance - Apply logical thinking to problem solve - Ability to multi-task in a fast-paced work environment Benefits: - In addition to your salary, this position may be eligible for medical, dental, vision, retirement, and other fringe benefits. - Positions that require night, weekend or on-call work may be eligible for shift differentials or premium pay. Pay: - The posted salary represents a market competitive range based on salary survey benchmark data for similar roles in the local or national market. - Annual salaries displayed are based on full-time employment (40 standard hrs per week). - Annual salaries for part-time positions will be prorated based on the employee’s scheduled weekly hours