Jobs · Finance

Dermatology Access & Reimbursement Manager – Northern New Jersey

Novartis · Jersey City, NJ · 1 mo ago
RemoteRemoteFinanceFull-time
We need to output HTML fragment with sections: About the role (maybe heading "About the role" or "About The Role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections that have real content. We need to extract content from posting. First, we have a summary paragraph: "This is a field-based and remote opportunity supporting key accounts in an assigned geography. Novartis is unable to offer relocation support for this role. Please only apply if this location is accessible to you. Company will not sponsor visas for this position." This is likely metadata; we can fold into a short

maybe under "About the role"? Actually "About The Role" heading is present later. The summary could be part of "About the role". The posting includes "About The Role" heading then "Key Responsibilities:" list. We need to preserve all substantive info, not repeat job title, not include Job ID, etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statement, accessibility statement, etc. Also remove "Why Novartis:" paragraph? That may be considered boilerplate? It's marketing but maybe keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Novartis:" is not exactly those, but could be considered fluff. However we need to preserve ALL substantive information; not invent or summarize away detail. The "Why Novartis:" paragraph is substantive? It's more marketing but still part of posting. Might be okay to keep as a paragraph under maybe "About Novartis"? But we only have headings list; we could include a section "About Novartis" but not in list. The instruction says use headings for those examples; but we can also have other headings? 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 those. Safer to stick to those headings if content exists. We have content for: - About the role: includes summary paragraph and maybe description of role: "The Access & Reimbursement Manager (ARM) is a field-based partner who provides education and support to healthcare accounts on access, reimbursement, coverage, billing, coding, and patient support resources that help patients access prescribed therapies. Serving as the local market access expert, the Access & Reimbursement Manager proactively identifies and resolves reimbursement challenges, analyzes evolving healthcare trends, and helps integrate support programs into account workflows. This role collaborates closely with customers and cross-functional partners to deliver solutions that enhance the patient and provider experience. The Access & Reimbursement Manager also works alongside field and home-office teams, representing Novartis with integrity, collaboration, and a commitment to improving access to care." That's substantive. - Responsibilities: list under "Key Responsibilities:" with bullet points. - Requirements: list under "Essential Requirements" with bullet points. - Qualifications? Not separate; maybe "Essential Requirements" covers qualifications. Could also have "Skills" but not explicit. - Benefits: there is a "Novartis Compensation Summary" with salary range placeholder $XXX and $XXX (not actual numbers). Since it's placeholder, we should NOT create Pay section unless posting actually states them. It says salary range expected between $XXX and $XXX per year. That's placeholder; we should not include Pay section because it's not specific. Also benefits: "Your compensation will include a performance-based cash incentive and, depending on the level of the role, eligibility to be considered for annual equity awards. US-based eligible employees will receive a comprehensive benefits package that includes health, life and disability benefits, a 401(k) with company contribution and match, and a variety of other benefits. In addition, employees are eligible for a generous time off package including vacation, personal days, holidays and other leaves." That's substantive benefits info. So we should include a Benefits section. - Schedule: there is travel requirement: "Ability to travel 60-80% over a broad geography is required, with the ability to drive and/or fly within the territory." Also "Candidate must reside within territory, or within a reasonable daily commuting distance of 50 miles from the territory border." Also "Must have a valid driver’s license." That's schedule/travel info. Could be under Schedule section. Also "For Field Roles with a Dedicated Training Period: The individual hired for this role will be required to successfully complete certain initial training, including home study in eight (8) or fewer hours per day and forty (40) or fewer hours per week." That's also schedule/training. Thus we can have Schedule section. - Pay: we should not include because placeholder. - Skills: maybe not explicit; we could combine into Requirements. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We need to output only HTML fragment, no /, no markdown fences. We'll produce:

About the role

... (summary + role description)

Responsibilities

  • ...
  • ...

Requirements

  • ...
  • ...

Benefits

... (benefits description)

Schedule

... (travel, residence, driver license, training)

We need to ensure we preserve all substantive info from posting, not invent or summarize away detail. Let's extract exact sentences. Summary paragraph: "This is a field-based and remote opportunity supporting key accounts in an assigned geography. Novartis is unable to offer relocation support for this role. Please only apply if this location is accessible to you. Company will not sponsor visas for this position." We can include that as part of About the role. Then the role description paragraph(s) after "About The Role". Actually after "About The Role" heading, there is a paragraph: "The Access & Reimbursement Manager (ARM) is a field-based partner who provides education and support to healthcare accounts on access, reimbursement, coverage, billing, coding, and patient support resources that help patients access prescribed therapies. Serving as the local market access expert, the Access & Reimbursement Manager proactively identifies and resolves reimbursement challenges, analyzes evolving healthcare trends, and helps integrate support programs into account workflows. This role collaborates closely with customers and cross-functional partners to deliver solutions that enhance the patient and provider experience. The Access & Reimbursement Manager also works alongside field and home-office teams, representing Novartis with integrity, collaboration, and a commitment to improving access to care." We'll combine summary and that into About the role paragraph(s). Could be two

elements or one. We'll keep as separate paragraphs for readability. Now Responsibilities list: after "Key Responsibilities:" there are bullet points each starting with a verb. Let's capture each: - Partner with healthcare providers, practice leaders, billing teams, and other stakeholders to support patient access to prescribed therapies and treatment-related resources. - Deliver education and guidance on access, reimbursement, coverage, and patient support programs, helping integrate these resources into office workflows and processes. - Serve as a resource for questions related to product acquisition, ordering, payment, inventory management, and product return and replacement processes. - Collaborate with customer accounts to navigate reimbursement, claims, prior authorization, denial, appeal, and coverage-related challenges, helping identify practical solutions that support patient access. - Monitor and communicate changes in payer policies, reimbursement trends, and the evolving healthcare landscape that may impact patients, providers, or internal stakeholders. - Support the implementation of patient assistance and co-pay programs, helping patients start and remain on appropriate therapy. - Partner with Patient Support Services and other cross-functional teams to resolve access and reimbursement issues, track cases, and provide education that enhances the customer experience. - Develop and execute account-specific access and reimbursement plans, including support for buy-and-bill processes, acquisition pathways, and site-of-care considerations across diverse healthcare settings. - Build relationships with a broad range of non-prescribing stakeholders, including revenue cycle leaders, financial counselors, pharmacists, office administrators, and health system decision-makers. - Share customer insights, market trends, and access barriers with internal partners while ensuring compliance with all applicable policies, regulations, and adverse event reporting requirements. We'll put each as

  • . Now Requirements: after "Essential Requirements" heading, bullet points: - Bachelor’s degree required from 4-year college or university. - 3+ years of experience in reimbursement, market access, managed care, clinical support, pharmaceutical sales, or a related healthcare environment. - Experience supporting specialty pharmacy products through specialty pharmacy networks, distributors, or other specialty access channels. - Knowledge of coding, billing, claims, reimbursement processes, and office-based patient support programs. - Experience partnering with specialty pharmacies and navigating access and reimbursement considerations across the patient journey. - Understanding of buy-and-bill reimbursement pathways, including product acquisition, coverage, and payment processes. - Experience working with injection networks or provider-administered therapies in physician office, clinic, or health system settings. - Candidate must reside within territory, or within a reasonable daily commuting distance of 50 miles from the territory border. - Ability to travel 60-80% over a broad geography is required, with the ability to drive and/or fly within the territory. - Must have a valid driver’s license. - Driving is an Essential Function of this Role: Meaning it is fundamental to the purpose of this job and cannot be eliminated. Because driving is an essential function of the role, you must have a fully valid and unrestricted driver’s license to be qualified for this role. The company provides reasonable accommodations for otherwise qualified individuals with medical restrictions if an accommodation can be provided without eliminating the essential function of driving. - COVID-19 Vaccine Policy (customer-facing roles only): While Novartis does not require vaccination for COVID-19 or proof of a recent negative test result for COVID-19 at this time, employees working in customer-facing roles must adhere to and comply with customers’ (such as hospitals, physician offices, etc.) credentialing guidelines, which may require vaccination. As required by applicable law, Novartis will consider requests for reasonable accommodation for those unable to be vaccinated. This requirement is subject to applicable state and local laws and may not be applicable to employees working in certain jurisdictions. Please send accommodation requests to Eh.occupationalhealth@novartis.com. - For Field Roles with a Dedicated Training Period: The individual hired for this role will be required to successfully complete certain initial training, including home study in eight (8) or fewer hours per day and forty (40) or fewer hours per week. We need to decide what to include in Requirements vs Schedule. The travel, residence, driver license, driving essential function, COVID vaccine policy, training could be considered schedule or other. But we have a Schedule section for travel/training etc. However the instruction says use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put travel/residence/driver license under Schedule. The COVID vaccine policy maybe could be under Requirements? It's a policy requirement. Could be under Requirements as well. But we need to avoid duplication. Let's think: The posting includes "Essential Requirements" list that includes many items, including residence, travel, driver license, driving essential function, COVID vaccine policy, training. If we move some to Schedule, we might be omitting from Requirements. But we could keep all under Requirements and not have Schedule. However we have schedule info like travel 60-80% etc. That is also in Requirements. So we could just have Requirements section covering all those. Then we might not need a separate Schedule section. But we also have benefits section. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine travel/residence/driver license/training into Requirements. Then
  • Similar jobs