Patient Care Concierge I
Claremedica · Palm Beach Gardens, FL · 1 mo ago
OTHRFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro about Claremedica, then "Essential Functions", "Duties And Responsibilities", "Supervisory Responsibilities", "Qualifications", "WORKING CONDITIONS", "PHYSICAL DEMANDS", "WORK ENVIRONMENT", "TRAVEL", "SAFETY HAZARD OF THE JOB". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can only include sections that have real specific content. We have responsibilities (duties). We have qualifications (requirements). We have skills maybe within qualifications. We have no explicit benefits, pay, schedule. So we should not include those sections. Also we may include "About the role" from intro paragraph. The intro includes mission etc. That can be About the role. We'll put that in
About the role
withcontaining the intro paragraphs (maybe combine). Then Responsibilities: list duties. Use
- . Qualifications: list qualifications. Use
- . Possibly also Skills: but we can embed within qualifications. Better to keep Qualifications section only.
We must not repeat job title. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We must preserve all substantive information. So we need to include all duties, qualifications, working conditions, physical demands, work environment, travel, safety hazard. Those are substantive but not in allowed headings. However instructions: Use headings only from list. But we must preserve all substantive information; we can put them under appropriate headings like Responsibilities or Qualifications or maybe under About the role? But we cannot invent headings. We could put extra info under Responsibilities (maybe as subpoints) or Qualifications. However some info like working conditions, physical demands, travel, safety hazard are not responsibilities or qualifications. But we could still include them as part of Responsibilities? Might be stretching. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but likely only those allowed. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we must decide which sections to include based on content. The posting has content for About the role (intro), Responsibilities (duties), Qualifications (requirements/skills). It also has content for Working Conditions, Physical Demands, Work Environment, Travel, Safety Hazard. Those are not in the allowed list, but maybe we can treat them as part of Responsibilities or Qualifications? The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems those are the only headings we should use. So we must fit all info into those categories. Could we put Working Conditions etc under Responsibilities? Not ideal but maybe acceptable. However we could also create a section "Requirements" for qualifications, and "Skills" for skills. The posting includes qualifications and skills intermixed. We could split: Requirements = minimum qualifications (HS diploma, experience, BLS preferred). Skills = communication, organization, etc. But we have to avoid filler. Better approach: Use About the role (intro), Responsibilities (duties), Requirements (minimum qualifications), Skills (preferred skills/abilities). That covers most. Working conditions etc could be omitted? But we must preserve ALL substantive information. So we need to include them somewhere. Could we include them under Responsibilities as additional duties? Eg "Maintain cleanliness of space" is already a duty. Others like physical demands, work environment, travel, safety hazard are not duties but could be considered part of the role description. Could be placed under About the role as additional context. That might be acceptable: About the role can include description of work environment, physical demands, travel, safety. So we can expand About the role paragraph to include those details. Thus we will have:
About the role
Claremedica mission intro + plus working conditions, physical demands, work environment, travel, safety hazard.
Responsibilities
- ... duties list
Requirements
- HS diploma/GED, 1 year experience in medical clinic or customer service, BLS preferred, ability to type 40 WPM, etc (minimum).
Skills
- Exceptional oral/written communication, time management, organizational skills, ability to communicate professionally, problem solving mindset, knowledge of medical terminology, ability to act calmly, strong listening, proficiency with MS Office, ability to travel up to 10%, bilingual plus, HIPAA/AHCA experience preferred, healthcare experience preferred, EMR experience preferred, ability to read/write English, etc.
- . Possibly also Skills: but we can embed within qualifications. Better to keep Qualifications section only.
We must not repeat job title. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We must preserve all substantive information. So we need to include all duties, qualifications, working conditions, physical demands, work environment, travel, safety hazard. Those are substantive but not in allowed headings. However instructions: Use headings only from list. But we must preserve all substantive information; we can put them under appropriate headings like Responsibilities or Qualifications or maybe under About the role? But we cannot invent headings. We could put extra info under Responsibilities (maybe as subpoints) or Qualifications. However some info like working conditions, physical demands, travel, safety hazard are not responsibilities or qualifications. But we could still include them as part of Responsibilities? Might be stretching. The instruction: "Use