Oasis Reviewer - Home Health
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, remove boilerplate (EEO, E-verify, etc). Also remove cookie/navigation/legal etc. The posting includes some EEO statements at end; we should remove them. Also remove "If you are unable to submit an application..." etc. Also remove "Mosai is an equal opportunity employer." etc. Also remove "Mosai is an E-verify employer." etc.
We need to include sections only when posting has real specific content. All sections have content.
We need to format content appropriately: For each section, we can have
Section Title
then either paragraphs or
- for lists.
We need to decide what constitutes a list. The job duties are a series of sentences each starting with a verb; could be turned into
- . Similarly Minimum Requirements could be a list. Preferred Skills also list. Work Environment maybe prose. Physical Demands maybe list? It's a paragraph describing demands; could keep as
. We'll convert duties, requirements, preferred skills to lists.
We must not invent or summarize away detail. Keep all details.
Let's extract content.
About Mosai: first paragraph: "About Mosai Mosai™ is the intelligent care coordination platform that brings together the fragmented pieces of healthcare into a clear, connected picture. Like a mosaic, our platform unites data, people, and processes so providers can make better decisions, coordinate care in real time, and deliver improved outcomes. With Mosai, home-based care organizations can thrive in value-based care while giving every patient the right care, in the right place, at the right time. Learn more at https://www.mosai.com/"
We can put that as
under maybe "About Mosai"? But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but not strict; they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings if applicable. However the posting has sections like "About Mosai", "Position Summary", "Job Duties", "Minimum Requirements", "Work Environment", "Preferred Skills And Experience", "Physical Demands of Our Work Environment". We need to map to allowed headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings, but not required to exactly match; we can use similar headings that reflect content. Probably we should use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", etc. But the posting already has headings; we could keep them as is but they must be . 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 suggests using those. Safer to use those standard headings. However we need to preserve all substantive information; we can reorder content under those headings.
Let's map:
- About the role: could include About Mosai and Position Summary combined.
- Responsibilities: Job Duties.
- Requirements: Minimum Requirements.
- Qualifications: maybe Preferred Skills And Experience? Or we could treat Preferred Skills as Qualifications. But they said Qualifications as a possible heading. We could put Preferred Skills under Qualifications.
- Skills: maybe Preferred Skills And Experience? Actually they listed Skills as a possible heading; we could put Preferred Skills there.
But we need to avoid duplication. Let's decide:
We'll create sections:
About the role
(contains About Mosai description and Position Summary)
Responsibilities
(Job Duties list)
Requirements
(Minimum Requirements list)
Qualifications
(Preferred Skills And Experience list)
We could also add a section for Work Environment and Physical Demands if they have substantive content. The instruction says include a section ONLY when the posting has real, specific content for it. Work Environment and Physical Demands have content. Should we include them? The examples didn't list Work Environment but we can still use for any section heading; they gave examples but not exclusive. So we can add sections for Work Environment and Physical Demands.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Work Environment, Physical Demands.
We must not include Benefits, Pay, Schedule as they are not present.
Now we need to extract content precisely.
About Mosai paragraph: "About Mosai Mosai™ is the intelligent care coordination platform that brings together the fragmented pieces of healthcare into a clear, connected picture. Like a mosaic, our platform unites data, people, and processes so providers can make better decisions, coordinate care in real time, and deliver improved outcomes. With Mosai, home-based care organizations can thrive in value-based care while giving every patient the right care, in the right place, at the right time. Learn more at https://www.mosai.com/"
Position Summary: "Performs clinical review and validation of OASIS assessments on behalf of contracted home health agency clients, working within Mosai’s AI-assisted review platform and each client’s electronic medical record.Applies licensed clinical judgment to independently verify platform-generated findings against the source record and produce clear, defensible recommendations.May be assigned ICD-10 coding review as a secondary scope, based on credentials held and the services a given client has purchased.This is a production review role and is not client-facing; all questions, disagreements, and escalations route through Mosai clinical operations and the client services team."
Note there are no spaces after periods; we should keep as is but maybe add spaces for readability? We must preserve substantive information; we can keep the text exactly as given, but we could add spaces for clarity? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Adding spaces is not changing meaning, but could be considered altering. Safer to keep exactly as given, but it's hard to read. However we can keep as is; it's still substantive.
We'll combine About Mosai and Position Summary into a
maybe two paragraphs.
Responsibilities: list of duties. Let's extract each duty sentence:
- Conduct review using Mosai’s AI-assisted review platform, accessing source documentation in the platform and the client’s EMR as the assignment requires; independently verify every platform-generated finding against the record before including it in a recommendation.
- Review OASIS assessments across all required time points: Start of Care, Resumption of Care, Recertification, Transfer, and Discharge - validating responses against the current OASIS data set, CMS Guidance Manual, applicable skip logic, and CMS Quarterly OASIS Q&As.
- Verify internal consistency between OASIS responses and the supporting record, applying particular scrutiny to Section GG self-care and mobility items, cognitive and behavioral items, and case-mix-impacting M-items.
- Apply Patient-Driven Groupings Model (PDGM) requirements, including clinical grouping, functional impairment level, comorbidity adjustment, and LUPA exposure.
- Where credentialed, review primary and secondary diagnosis assignment against ICD-10-CM Official Guidelines and home health sequencing conventions as a secondary scope, escalating coding or OASIS conflicts to Mosai clinical operations.
- Produce written recommendations that state the item or code at issue, the supporting or conflicting documentation and its location in the record, applicable CMS or coding guidance, and clinical rationale — framed as compliant, non-leading requests that never direct a specific response.
- Enter recommendations through each client’s defined channel, meet contracted turnaround commitments, and track recommendations to closure.
- Work across multiple client agencies and EMR platforms, completing client-required onboarding and access provisioning before beginning review work for that client.
- Access and use protected health information only as necessary to perform assigned review work, consistent with HIPAA minimum necessary requirements and the applicable Business Associate Agreement; never enter, alter, or fabricate clinical documentation.
- Maintain review accuracy at or above the standard defined by Mosai clinical quality, participate in calibration exercises, and report platform false positives, missed findings, and out-of-date guidance references.
We'll put each as
- .
Requirements: Minimum Requirements list:
- Active, unrestricted Registered Nurse (RN) license required, in the state or states necessary to support assigned client work.
- Associate’s degree in Nursing required.
- Current COS-C (Certificate for OASIS Specialist – Clinical) or HCS-O (Home Care Clinical Specialist – OASIS) certification required, held at time of hire.
- Minimum of 3 years of clinical experience in Medicare-certified home health required, including hands-on completion or review of OASIS assessments.
- Hands-on experience with at least one major home health EMR (for example Homecare Homebase, WellSky, Axxess, or KanTime) required.
- Demonstrated working knowledge of PDGM, HIPPS and case-mix assignment, LUPA thresholds, CMS Conditions of Participation, and OASIS-based quality measures.
- Ability to critically evaluate AI-generated findings and disagree with the platform when the record does not support it; strong written communication, high attention to detail, and the ability to work independently in a remote environment while meeting daily throughput targets.
We'll list each as
- .
Qualifications: Preferred Skills And Experience list:
- BSN preferred; multi-state RN licensure or eligibility for licensure in additional states strongly preferred, with Nurse Licensure Compact participation preferred.
- Current HCS-D (Home Care Coding Specialist – Diagnosis) certification for ICD-10 coding review as a secondary scope; an OASIS credential and HCS-D together preferred, with BCHH-C or COQS considered as equivalents.
- Dedicated OASIS review, QA, or clinical audit experience; prior experience in an outsourced, vendor, or multi-client review environment.
- Hands-on experience with two or more major home health EMR systems strongly preferred, as this role works directly in multiple client systems.
- Experience using clinical software, decision support, or AI-assisted review tools, with a demonstrated ability to learn new platforms quickly.
We'll list each as
- .
Work Environment: paragraph:
"This is a hybrid role based in Nashville or Jacksonville.Primarily sedentary work performed in a remote or office setting, with extended periods of computer and screen use.This is a production review role and is not client-facing; all questions and escalations route through Mosai clinical operations and the client services team.Remote work requires a secure, private workspace and a reliable internet connection meeting Mosai and client security standards.Occasional travel for training or team meetings; no client site visits required.All activity in Mosai products and client EMRs is logged and auditable, and record access is subject to client and Mosai audit at any time."
Note missing spaces after periods; we keep as is.
Physical Demands of Our Work Environment: paragraph:
"This position uses a computer and other office equipment as needed to perform duties. The in-office noise level in the work environment is typical of that of an office. Frequent interruptions may be encountered throughout the workday. The employee is required to either stand or sit, talk and hear frequently required to use repetitive keying or hand motions. The physical demands are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions."
We'll put as
.
Now
for prose. We need to preserve all substantive information, remove boilerplate (EEO, E-verify, etc). Also remove cookie/navigation/legal etc. The posting includes some EEO statements at end; we should remove them. Also remove "If you are unable to submit an application..." etc. Also remove "Mosai is an equal opportunity employer." etc. Also remove "Mosai is an E-verify employer." etc. We need to include sections only when posting has real specific content. All sections have content. We need to format content appropriately: For each section, we can have
Section Title
then eitherparagraphs or
- for lists.
We need to decide what constitutes a list. The job duties are a series of sentences each starting with a verb; could be turned into
- . Similarly Minimum Requirements could be a list. Preferred Skills also list. Work Environment maybe prose. Physical Demands maybe list? It's a paragraph describing demands; could keep as
. We'll convert duties, requirements, preferred skills to lists. We must not invent or summarize away detail. Keep all details. Let's extract content. About Mosai: first paragraph: "About Mosai Mosai™ is the intelligent care coordination platform that brings together the fragmented pieces of healthcare into a clear, connected picture. Like a mosaic, our platform unites data, people, and processes so providers can make better decisions, coordinate care in real time, and deliver improved outcomes. With Mosai, home-based care organizations can thrive in value-based care while giving every patient the right care, in the right place, at the right time. Learn more at https://www.mosai.com/" We can put that as
under maybe "About Mosai"? But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but not strict; they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings if applicable. However the posting has sections like "About Mosai", "Position Summary", "Job Duties", "Minimum Requirements", "Work Environment", "Preferred Skills And Experience", "Physical Demands of Our Work Environment". We need to map to allowed headings? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings, but not required to exactly match; we can use similar headings that reflect content. Probably we should use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", etc. But the posting already has headings; we could keep them as is but they must be
. 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 suggests using those. Safer to use those standard headings. However we need to preserve all substantive information; we can reorder content under those headings. Let's map: - About the role: could include About Mosai and Position Summary combined. - Responsibilities: Job Duties. - Requirements: Minimum Requirements. - Qualifications: maybe Preferred Skills And Experience? Or we could treat Preferred Skills as Qualifications. But they said Qualifications as a possible heading. We could put Preferred Skills under Qualifications. - Skills: maybe Preferred Skills And Experience? Actually they listed Skills as a possible heading; we could put Preferred Skills there. But we need to avoid duplication. Let's decide: We'll create sections:
About the role
(contains About Mosai description and Position Summary)Responsibilities
(Job Duties list)Requirements
(Minimum Requirements list)Qualifications
(Preferred Skills And Experience list) We could also add a section for Work Environment and Physical Demands if they have substantive content. The instruction says include a section ONLY when the posting has real, specific content for it. Work Environment and Physical Demands have content. Should we include them? The examples didn't list Work Environment but we can still usefor any section heading; they gave examples but not exclusive. So we can add sections for Work Environment and Physical Demands. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Work Environment, Physical Demands. We must not include Benefits, Pay, Schedule as they are not present. Now we need to extract content precisely. About Mosai paragraph: "About Mosai Mosai™ is the intelligent care coordination platform that brings together the fragmented pieces of healthcare into a clear, connected picture. Like a mosaic, our platform unites data, people, and processes so providers can make better decisions, coordinate care in real time, and deliver improved outcomes. With Mosai, home-based care organizations can thrive in value-based care while giving every patient the right care, in the right place, at the right time. Learn more at https://www.mosai.com/" Position Summary: "Performs clinical review and validation of OASIS assessments on behalf of contracted home health agency clients, working within Mosai’s AI-assisted review platform and each client’s electronic medical record.Applies licensed clinical judgment to independently verify platform-generated findings against the source record and produce clear, defensible recommendations.May be assigned ICD-10 coding review as a secondary scope, based on credentials held and the services a given client has purchased.This is a production review role and is not client-facing; all questions, disagreements, and escalations route through Mosai clinical operations and the client services team." Note there are no spaces after periods; we should keep as is but maybe add spaces for readability? We must preserve substantive information; we can keep the text exactly as given, but we could add spaces for clarity? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Adding spaces is not changing meaning, but could be considered altering. Safer to keep exactly as given, but it's hard to read. However we can keep as is; it's still substantive. We'll combine About Mosai and Position Summary into a
maybe two paragraphs. Responsibilities: list of duties. Let's extract each duty sentence: - Conduct review using Mosai’s AI-assisted review platform, accessing source documentation in the platform and the client’s EMR as the assignment requires; independently verify every platform-generated finding against the record before including it in a recommendation. - Review OASIS assessments across all required time points: Start of Care, Resumption of Care, Recertification, Transfer, and Discharge - validating responses against the current OASIS data set, CMS Guidance Manual, applicable skip logic, and CMS Quarterly OASIS Q&As. - Verify internal consistency between OASIS responses and the supporting record, applying particular scrutiny to Section GG self-care and mobility items, cognitive and behavioral items, and case-mix-impacting M-items. - Apply Patient-Driven Groupings Model (PDGM) requirements, including clinical grouping, functional impairment level, comorbidity adjustment, and LUPA exposure. - Where credentialed, review primary and secondary diagnosis assignment against ICD-10-CM Official Guidelines and home health sequencing conventions as a secondary scope, escalating coding or OASIS conflicts to Mosai clinical operations. - Produce written recommendations that state the item or code at issue, the supporting or conflicting documentation and its location in the record, applicable CMS or coding guidance, and clinical rationale — framed as compliant, non-leading requests that never direct a specific response. - Enter recommendations through each client’s defined channel, meet contracted turnaround commitments, and track recommendations to closure. - Work across multiple client agencies and EMR platforms, completing client-required onboarding and access provisioning before beginning review work for that client. - Access and use protected health information only as necessary to perform assigned review work, consistent with HIPAA minimum necessary requirements and the applicable Business Associate Agreement; never enter, alter, or fabricate clinical documentation. - Maintain review accuracy at or above the standard defined by Mosai clinical quality, participate in calibration exercises, and report platform false positives, missed findings, and out-of-date guidance references. We'll put each as
- . Requirements: Minimum Requirements list: - Active, unrestricted Registered Nurse (RN) license required, in the state or states necessary to support assigned client work. - Associate’s degree in Nursing required. - Current COS-C (Certificate for OASIS Specialist – Clinical) or HCS-O (Home Care Clinical Specialist – OASIS) certification required, held at time of hire. - Minimum of 3 years of clinical experience in Medicare-certified home health required, including hands-on completion or review of OASIS assessments. - Hands-on experience with at least one major home health EMR (for example Homecare Homebase, WellSky, Axxess, or KanTime) required. - Demonstrated working knowledge of PDGM, HIPPS and case-mix assignment, LUPA thresholds, CMS Conditions of Participation, and OASIS-based quality measures. - Ability to critically evaluate AI-generated findings and disagree with the platform when the record does not support it; strong written communication, high attention to detail, and the ability to work independently in a remote environment while meeting daily throughput targets. We'll list each as
- . Qualifications: Preferred Skills And Experience list: - BSN preferred; multi-state RN licensure or eligibility for licensure in additional states strongly preferred, with Nurse Licensure Compact participation preferred. - Current HCS-D (Home Care Coding Specialist – Diagnosis) certification for ICD-10 coding review as a secondary scope; an OASIS credential and HCS-D together preferred, with BCHH-C or COQS considered as equivalents. - Dedicated OASIS review, QA, or clinical audit experience; prior experience in an outsourced, vendor, or multi-client review environment. - Hands-on experience with two or more major home health EMR systems strongly preferred, as this role works directly in multiple client systems. - Experience using clinical software, decision support, or AI-assisted review tools, with a demonstrated ability to learn new platforms quickly. We'll list each as
- .
Work Environment: paragraph:
"This is a hybrid role based in Nashville or Jacksonville.Primarily sedentary work performed in a remote or office setting, with extended periods of computer and screen use.This is a production review role and is not client-facing; all questions and escalations route through Mosai clinical operations and the client services team.Remote work requires a secure, private workspace and a reliable internet connection meeting Mosai and client security standards.Occasional travel for training or team meetings; no client site visits required.All activity in Mosai products and client EMRs is logged and auditable, and record access is subject to client and Mosai audit at any time."
Note missing spaces after periods; we keep as is.
Physical Demands of Our Work Environment: paragraph:
"This position uses a computer and other office equipment as needed to perform duties. The in-office noise level in the work environment is typical of that of an office. Frequent interruptions may be encountered throughout the workday. The employee is required to either stand or sit, talk and hear frequently required to use repetitive keying or hand motions. The physical demands are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions."
We'll put as
. Now
- . Similarly Minimum Requirements could be a list. Preferred Skills also list. Work Environment maybe prose. Physical Demands maybe list? It's a paragraph describing demands; could keep as