Digital Product Analyst
Quest Diagnostics · Irving, TX · 1 mo ago
AnalystFull-time
We need to output HTML fragment with headings for sections present: About the role? Actually the posting includes "Job Description" then description. There's no explicit "About the role" heading but we can treat the initial paragraph as maybe "About the role". However instruction: Use
for sections present: About the role? Actually the posting includes "Job Description" then description. There's no explicit "About the role" heading but we can treat the initial paragraph as maybe "About the role". However instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when the posting has real, specific content for it. So we need to decide which sections exist.
We have content: Job Description paragraph (intro). Then "Responsibilities" with sub-bullets. Then "Qualifications" with sub-sections: Education Required, Required Work Experience, Preferred Work Experience, Knowledge & Technical Expertise. Then "Skills". Then "About The Team" (which includes some EEO etc). Also there is some boilerplate about veterans, equal opportunity, etc which we should remove (EEO/equal-opportunity). Also "About The Team" includes some content that is not boilerplate? It says: "Quest Diagnostics honors our service members and encourages veterans to apply. While we appreciate and value our staffing partners, we do not accept unsolicited resumes from agencies. Quest will not be responsible for paying agency fees for any individual as to whom an agency has sent an unsolicited resume." That's somewhat boilerplate but maybe we keep? It's not EEO but it's about agency resumes. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About The Team" includes some legal-ish statements about agency fees. Might be considered legal boilerplate. Safer to remove that entire "About The Team" section? But we need to preserve substantive information. The substantive part is maybe none. The EEO line also present: "Equal Opportunity Employer: Race/Color/Sex/Sexual Orientation/Gender Identity/Religion/National Origin/Disability/Vets or any other legally protected status." That's EEO boilerplate, remove.
Thus we may not have a substantive "About The Team" section after removal. So we may omit that section.
We have sections: Responsibilities, Qualifications, Skills. Possibly also "About the role" from the introductory paragraph. The instruction says use for section headings (e.g. About the role, Responsibilities...). So we can include an "About the role" heading with the intro paragraph.
We must not repeat the job title as a heading (the page already shows it). So we don't add a heading for job title.
We must not put Job ID/requisition numbers as headings (none present).
We must use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment.
Let's extract content.
Intro paragraph: "This role is a critical piece in our Product organization that helps to translate strategy into action as we work to make the digital experience at Quest universally lovable for all of our constituents. We believe that a passion for enjoyable experiences is core to helping us achieve our goals, which in turn will lead to new growth opportunities for Quest to explore. The Digital Product Analyst, Interoperability will be responsible for defining, developing, and executing strategies to integrate and scale healthcare interoperability products, channels, and API data exchanges. In this role, you will analyze complex clinical data workflows, conduct market and EHR-vendor research, and couple these insights with internal technical mapping to propose innovative, scalable connectivity solutions for our partners, physicians, and health systems. Collaborating closely with Product Managers, Interface Engineers, and Software Developers, the Senior Analyst acts as a critical bridge to bring high-impact data exchange features to life, accelerating clinical integrations, electronic health record (EHR) partner onboarding, and strategic client migrations."
That's the intro.
Now Responsibilities: It has headings within: Interoperability Strategy & Analysis, Product Delivery & Agile Execution, Collaboration & Innovation. Under each there are bullet points (some are sentences). We need to represent as
- . The headings within responsibilities could be treated as maybe
but instruction only mentions for section headings. We could keep them as or just plain text inside - . Probably better to keep as plain text.
Thus we will create
Responsibilities
then with each bullet as - . Need to capture all bullet points.
Let's list them:
Under Interoperability Strategy & Analysis:
- Data Flow & Workflow Analysis: Lead the mapping, analysis, and optimization of complex clinical data flows (e.g., orders, discrete results, genomic data) across internal laboratory information systems (LIS) and external EMR/EHR platforms.
- EHR Integration & Onboarding: Partner with primary EHR vendors and healthcare networks to analyze integration capabilities, define connectivity requirements, and support strategic client migration or transition initiatives.
- Industry Standards Advocacy: Keep abreast of emerging healthcare interoperability guidelines, national standards, and regulations (such as HL7, FHIR, JSON APIs, and HIPAA) to ensure digital products remain leading-edge and compliant.
- Adoption & Growth Analytics: Conduct research and utilize analytical tools to monitor how healthcare providers interact with digital connectivity channels; identify factors that drive product adoption, integration speed, and clinical customer engagement.
Under Product Delivery & Agile Execution:
- Backlog Management & Story Writing: Write highly descriptive features and user stories centered on technical integrations, API requirements, and system interfaces, aligning with the "Definition Ready" and "Definition of Done."
- Agile Collaboration: Guide agile software engineering and interface squads through story refinement, daily standups, and release planning.
- Technical Roadmapping: Support Product Managers in prioritizing and detailing the interoperability product roadmap, using customer-centric design to minimize implementation barriers.
Under Collaboration & Innovation:
- Stakeholder Alignment: Coordinate cross-functionally with technical writers, data scientists, security experts, and business partners to design highly scalable, highly secure data transmission infrastructures.
- External Partner Liaison: Collaborate with third-party digital health networks, clinical databases, and external technology consultants to build seamless data bridges.
- Best Practices Leadership: Institutionalize best practices for interface implementation and digital product support, helping the organization transition from legacy integration processes to modern, scalable frameworks.
Now Qualifications: It has subheadings: Education Required, Required Work Experience, Preferred Work Experience, Knowledge & Technical Expertise.
We need to capture all.
Education Required: "Bachelor’s degree in Computer Science, Health Informatics, Information Technology, Business, or a related field. Equivalent, highly relevant work experience can substitute for the degree."
Required Work Experience: "Required: 3+ years of digital product analysis, healthcare IT analyst, or interface engineering experience. Required: At least 1–2 years of direct experience working on healthcare interoperability solutions (such as clinical interface engines, laboratory integrations, or EMR/EHR interfaces)."
Note there are two "Required:" lines; we can combine.
Preferred Work Experience: "Demonstrated success handling complex client-facing software migrations or vendor integrations. Hands-on experience working directly with major EMR/EHR platforms (e.g., Epic, Cerner, OncoEMR) and digital health integration networks. Experience navigating clinical lab networks or specialty diagnostic platforms (e.g., Precision Oncology, Pathology workflows)."
Knowledge & Technical Expertise: bullet list:
- Standards & Protocols: Strong knowledge of healthcare data exchange standards (HL7 v2/v3, FHIR, JSON APIs, XML, and C-CDA).
- Lab Workflows: Firm understanding of clinical lab operations, computerized physician order entry (CPOE), and structured lab results delivery.
- Agile Frameworks: In-depth knowledge of Agile/Scrum development methodologies, product owner responsibilities, and sprint management.
- Change Management: High awareness of change management practices when transitioning clinical users to new systems or data networks.
Now Skills: bullet list:
- Analytical Thinking: Exceptional capability to dissect complex datasets, identify clinical data elements, map system schemas, and produce actionable integration recommendations.
- Interpersonal & Communication: Stellar verbal and written communication skills with a proven ability to explain deep technical integrations to business stakeholders, and complex business workflows to developers.
- Business Process Mapping (BPM): Deep proficiency in visual business process mapping, workflow charting, and detailing clinical system integration touchpoints.
- Analytical Toolsets: Advanced experience utilizing data modeling, reporting, and analysis tools (e.g., Excel pivot tables, SQL, Tableau, Power BI, or workflow visualization software).
- Self-Direction: Highly organized, self-motivated, and capable of operating independently to drive projects to completion while maintaining close alignment with core product goals.
Now we need to output HTML fragment with
sections for About the role, Responsibilities, Qualifications, Skills. No Benefits, Pay, Schedule as not present.
We must not include any boilerplate like EEO, agency, veterans, etc.
Thus final HTML:
About the role
...intro paragraph...
Responsibilities
- Data Flow & Workflow Analysis: Lead the mapping, analysis, and optimization of complex clinical data flows (e.g., orders, discrete results, genomic data) across internal laboratory information systems (LIS) and external EMR/EHR platforms.
- EHR Integration & Onboarding: Partner with primary EHR vendors and healthcare networks to analyze integration capabilities, define connectivity requirements, and support strategic client migration or transition initiatives.
- Industry Standards Advocacy: Keep abreast of emerging healthcare interoperability guidelines, national standards, and regulations (such as HL7, FHIR, JSON APIs, and HIPAA) to ensure digital products remain leading-edge and compliant.
- Adoption & Growth Analytics: Conduct research and utilize analytical tools to monitor how healthcare providers interact with digital connectivity channels; identify factors that drive product adoption, integration speed, and clinical customer engagement.
- Backlog Management & Story Writing: Write highly descriptive features and user stories centered on technical integrations, API requirements, and system interfaces, aligning with the "Definition Ready" and "Definition of Done."
- Agile Collaboration: Guide agile software engineering and interface squads through story refinement, daily standups, and release planning.
- Technical Roadmapping: Support Product Managers in prioritizing and detailing the interoperability product roadmap, using customer-centric design to minimize implementation barriers.
- Stakeholder Alignment: Coordinate cross-functionally with technical writers, data scientists, security experts, and business partners to design highly scalable, highly secure data transmission infrastructures.
- External Partner Liaison: Collaborate with third-party digital health networks, clinical databases, and external technology consultants to build seamless data bridges.
- Best Practices Leadership: Institutionalize best practices for interface implementation and digital product support, helping the organization transition from legacy integration processes to modern, scalable frameworks.
Qualifications
Education Required: Bachelor’s degree in Computer Science, Health Informatics, Information Technology, Business, or a related field. Equivalent, highly relevant work experience can substitute for the degree.
Required Work Experience: Required: 3+ years of digital product analysis, healthcare IT analyst, or interface engineering experience. Required: At least 1–2 years of direct experience working on healthcare interoperability solutions (such as clinical interface engines, laboratory integrations, or EMR/EHR interfaces).
Preferred Work Experience: Demonstrated success handling complex client-facing software migrations or vendor integrations. Hands-on experience working directly with major EMR/EHR platforms (e.g., Epic, Cerner, OncoEMR) and digital health integration networks. Experience navigating clinical lab networks or specialty diagnostic platforms (e.g., Precision Oncology, Pathology workflows).
Knowledge & Technical Expertise: Standards & Protocols:
for section headings (e.g. About the role, Responsibilities...). So we can include an "About the role" heading with the intro paragraph.
We must not repeat the job title as a heading (the page already shows it). So we don't add a heading for job title.
We must not put Job ID/requisition numbers as headings (none present).
We must use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment.
Let's extract content.
Intro paragraph: "This role is a critical piece in our Product organization that helps to translate strategy into action as we work to make the digital experience at Quest universally lovable for all of our constituents. We believe that a passion for enjoyable experiences is core to helping us achieve our goals, which in turn will lead to new growth opportunities for Quest to explore. The Digital Product Analyst, Interoperability will be responsible for defining, developing, and executing strategies to integrate and scale healthcare interoperability products, channels, and API data exchanges. In this role, you will analyze complex clinical data workflows, conduct market and EHR-vendor research, and couple these insights with internal technical mapping to propose innovative, scalable connectivity solutions for our partners, physicians, and health systems. Collaborating closely with Product Managers, Interface Engineers, and Software Developers, the Senior Analyst acts as a critical bridge to bring high-impact data exchange features to life, accelerating clinical integrations, electronic health record (EHR) partner onboarding, and strategic client migrations."
That's the intro.
Now Responsibilities: It has headings within: Interoperability Strategy & Analysis, Product Delivery & Agile Execution, Collaboration & Innovation. Under each there are bullet points (some are sentences). We need to represent as
- . The headings within responsibilities could be treated as maybe
but instruction only mentions for section headings. We could keep them as or just plain text inside - . Probably better to keep as plain text.
Thus we will create
Responsibilities
then with each bullet as - . Need to capture all bullet points.
Let's list them:
Under Interoperability Strategy & Analysis:
- Data Flow & Workflow Analysis: Lead the mapping, analysis, and optimization of complex clinical data flows (e.g., orders, discrete results, genomic data) across internal laboratory information systems (LIS) and external EMR/EHR platforms.
- EHR Integration & Onboarding: Partner with primary EHR vendors and healthcare networks to analyze integration capabilities, define connectivity requirements, and support strategic client migration or transition initiatives.
- Industry Standards Advocacy: Keep abreast of emerging healthcare interoperability guidelines, national standards, and regulations (such as HL7, FHIR, JSON APIs, and HIPAA) to ensure digital products remain leading-edge and compliant.
- Adoption & Growth Analytics: Conduct research and utilize analytical tools to monitor how healthcare providers interact with digital connectivity channels; identify factors that drive product adoption, integration speed, and clinical customer engagement.
Under Product Delivery & Agile Execution:
- Backlog Management & Story Writing: Write highly descriptive features and user stories centered on technical integrations, API requirements, and system interfaces, aligning with the "Definition Ready" and "Definition of Done."
- Agile Collaboration: Guide agile software engineering and interface squads through story refinement, daily standups, and release planning.
- Technical Roadmapping: Support Product Managers in prioritizing and detailing the interoperability product roadmap, using customer-centric design to minimize implementation barriers.
Under Collaboration & Innovation:
- Stakeholder Alignment: Coordinate cross-functionally with technical writers, data scientists, security experts, and business partners to design highly scalable, highly secure data transmission infrastructures.
- External Partner Liaison: Collaborate with third-party digital health networks, clinical databases, and external technology consultants to build seamless data bridges.
- Best Practices Leadership: Institutionalize best practices for interface implementation and digital product support, helping the organization transition from legacy integration processes to modern, scalable frameworks.
Now Qualifications: It has subheadings: Education Required, Required Work Experience, Preferred Work Experience, Knowledge & Technical Expertise.
We need to capture all.
Education Required: "Bachelor’s degree in Computer Science, Health Informatics, Information Technology, Business, or a related field. Equivalent, highly relevant work experience can substitute for the degree."
Required Work Experience: "Required: 3+ years of digital product analysis, healthcare IT analyst, or interface engineering experience. Required: At least 1–2 years of direct experience working on healthcare interoperability solutions (such as clinical interface engines, laboratory integrations, or EMR/EHR interfaces)."
Note there are two "Required:" lines; we can combine.
Preferred Work Experience: "Demonstrated success handling complex client-facing software migrations or vendor integrations. Hands-on experience working directly with major EMR/EHR platforms (e.g., Epic, Cerner, OncoEMR) and digital health integration networks. Experience navigating clinical lab networks or specialty diagnostic platforms (e.g., Precision Oncology, Pathology workflows)."
Knowledge & Technical Expertise: bullet list:
- Standards & Protocols: Strong knowledge of healthcare data exchange standards (HL7 v2/v3, FHIR, JSON APIs, XML, and C-CDA).
- Lab Workflows: Firm understanding of clinical lab operations, computerized physician order entry (CPOE), and structured lab results delivery.
- Agile Frameworks: In-depth knowledge of Agile/Scrum development methodologies, product owner responsibilities, and sprint management.
- Change Management: High awareness of change management practices when transitioning clinical users to new systems or data networks.
Now Skills: bullet list:
- Analytical Thinking: Exceptional capability to dissect complex datasets, identify clinical data elements, map system schemas, and produce actionable integration recommendations.
- Interpersonal & Communication: Stellar verbal and written communication skills with a proven ability to explain deep technical integrations to business stakeholders, and complex business workflows to developers.
- Business Process Mapping (BPM): Deep proficiency in visual business process mapping, workflow charting, and detailing clinical system integration touchpoints.
- Analytical Toolsets: Advanced experience utilizing data modeling, reporting, and analysis tools (e.g., Excel pivot tables, SQL, Tableau, Power BI, or workflow visualization software).
- Self-Direction: Highly organized, self-motivated, and capable of operating independently to drive projects to completion while maintaining close alignment with core product goals.
Now we need to output HTML fragment with
sections for About the role, Responsibilities, Qualifications, Skills. No Benefits, Pay, Schedule as not present.
We must not include any boilerplate like EEO, agency, veterans, etc.
Thus final HTML:
About the role
...intro paragraph...
Responsibilities
- Data Flow & Workflow Analysis: Lead the mapping, analysis, and optimization of complex clinical data flows (e.g., orders, discrete results, genomic data) across internal laboratory information systems (LIS) and external EMR/EHR platforms.
- EHR Integration & Onboarding: Partner with primary EHR vendors and healthcare networks to analyze integration capabilities, define connectivity requirements, and support strategic client migration or transition initiatives.
- Industry Standards Advocacy: Keep abreast of emerging healthcare interoperability guidelines, national standards, and regulations (such as HL7, FHIR, JSON APIs, and HIPAA) to ensure digital products remain leading-edge and compliant.
- Adoption & Growth Analytics: Conduct research and utilize analytical tools to monitor how healthcare providers interact with digital connectivity channels; identify factors that drive product adoption, integration speed, and clinical customer engagement.
- Backlog Management & Story Writing: Write highly descriptive features and user stories centered on technical integrations, API requirements, and system interfaces, aligning with the "Definition Ready" and "Definition of Done."
- Agile Collaboration: Guide agile software engineering and interface squads through story refinement, daily standups, and release planning.
- Technical Roadmapping: Support Product Managers in prioritizing and detailing the interoperability product roadmap, using customer-centric design to minimize implementation barriers.
- Stakeholder Alignment: Coordinate cross-functionally with technical writers, data scientists, security experts, and business partners to design highly scalable, highly secure data transmission infrastructures.
- External Partner Liaison: Collaborate with third-party digital health networks, clinical databases, and external technology consultants to build seamless data bridges.
- Best Practices Leadership: Institutionalize best practices for interface implementation and digital product support, helping the organization transition from legacy integration processes to modern, scalable frameworks.
Qualifications
Education Required: Bachelor’s degree in Computer Science, Health Informatics, Information Technology, Business, or a related field. Equivalent, highly relevant work experience can substitute for the degree.
Required Work Experience: Required: 3+ years of digital product analysis, healthcare IT analyst, or interface engineering experience. Required: At least 1–2 years of direct experience working on healthcare interoperability solutions (such as clinical interface engines, laboratory integrations, or EMR/EHR interfaces).
Preferred Work Experience: Demonstrated success handling complex client-facing software migrations or vendor integrations. Hands-on experience working directly with major EMR/EHR platforms (e.g., Epic, Cerner, OncoEMR) and digital health integration networks. Experience navigating clinical lab networks or specialty diagnostic platforms (e.g., Precision Oncology, Pathology workflows).
Knowledge & Technical Expertise: Standards & Protocols:
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment. Let's extract content. Intro paragraph: "This role is a critical piece in our Product organization that helps to translate strategy into action as we work to make the digital experience at Quest universally lovable for all of our constituents. We believe that a passion for enjoyable experiences is core to helping us achieve our goals, which in turn will lead to new growth opportunities for Quest to explore. The Digital Product Analyst, Interoperability will be responsible for defining, developing, and executing strategies to integrate and scale healthcare interoperability products, channels, and API data exchanges. In this role, you will analyze complex clinical data workflows, conduct market and EHR-vendor research, and couple these insights with internal technical mapping to propose innovative, scalable connectivity solutions for our partners, physicians, and health systems. Collaborating closely with Product Managers, Interface Engineers, and Software Developers, the Senior Analyst acts as a critical bridge to bring high-impact data exchange features to life, accelerating clinical integrations, electronic health record (EHR) partner onboarding, and strategic client migrations." That's the intro. Now Responsibilities: It has headings within: Interoperability Strategy & Analysis, Product Delivery & Agile Execution, Collaboration & Innovation. Under each there are bullet points (some are sentences). We need to represent as
- . The headings within responsibilities could be treated as maybe
but instruction only mentions
for section headings. We could keep them as or just plain text inside
- . Probably better to keep as plain text. Thus we will create
Responsibilities
then- with each bullet as
- . Need to capture all bullet points.
Let's list them:
Under Interoperability Strategy & Analysis:
- Data Flow & Workflow Analysis: Lead the mapping, analysis, and optimization of complex clinical data flows (e.g., orders, discrete results, genomic data) across internal laboratory information systems (LIS) and external EMR/EHR platforms.
- EHR Integration & Onboarding: Partner with primary EHR vendors and healthcare networks to analyze integration capabilities, define connectivity requirements, and support strategic client migration or transition initiatives.
- Industry Standards Advocacy: Keep abreast of emerging healthcare interoperability guidelines, national standards, and regulations (such as HL7, FHIR, JSON APIs, and HIPAA) to ensure digital products remain leading-edge and compliant.
- Adoption & Growth Analytics: Conduct research and utilize analytical tools to monitor how healthcare providers interact with digital connectivity channels; identify factors that drive product adoption, integration speed, and clinical customer engagement.
Under Product Delivery & Agile Execution:
- Backlog Management & Story Writing: Write highly descriptive features and user stories centered on technical integrations, API requirements, and system interfaces, aligning with the "Definition Ready" and "Definition of Done."
- Agile Collaboration: Guide agile software engineering and interface squads through story refinement, daily standups, and release planning.
- Technical Roadmapping: Support Product Managers in prioritizing and detailing the interoperability product roadmap, using customer-centric design to minimize implementation barriers.
Under Collaboration & Innovation:
- Stakeholder Alignment: Coordinate cross-functionally with technical writers, data scientists, security experts, and business partners to design highly scalable, highly secure data transmission infrastructures.
- External Partner Liaison: Collaborate with third-party digital health networks, clinical databases, and external technology consultants to build seamless data bridges.
- Best Practices Leadership: Institutionalize best practices for interface implementation and digital product support, helping the organization transition from legacy integration processes to modern, scalable frameworks.
Now Qualifications: It has subheadings: Education Required, Required Work Experience, Preferred Work Experience, Knowledge & Technical Expertise.
We need to capture all.
Education Required: "Bachelor’s degree in Computer Science, Health Informatics, Information Technology, Business, or a related field. Equivalent, highly relevant work experience can substitute for the degree."
Required Work Experience: "Required: 3+ years of digital product analysis, healthcare IT analyst, or interface engineering experience. Required: At least 1–2 years of direct experience working on healthcare interoperability solutions (such as clinical interface engines, laboratory integrations, or EMR/EHR interfaces)."
Note there are two "Required:" lines; we can combine.
Preferred Work Experience: "Demonstrated success handling complex client-facing software migrations or vendor integrations. Hands-on experience working directly with major EMR/EHR platforms (e.g., Epic, Cerner, OncoEMR) and digital health integration networks. Experience navigating clinical lab networks or specialty diagnostic platforms (e.g., Precision Oncology, Pathology workflows)."
Knowledge & Technical Expertise: bullet list:
- Standards & Protocols: Strong knowledge of healthcare data exchange standards (HL7 v2/v3, FHIR, JSON APIs, XML, and C-CDA).
- Lab Workflows: Firm understanding of clinical lab operations, computerized physician order entry (CPOE), and structured lab results delivery.
- Agile Frameworks: In-depth knowledge of Agile/Scrum development methodologies, product owner responsibilities, and sprint management.
- Change Management: High awareness of change management practices when transitioning clinical users to new systems or data networks.
Now Skills: bullet list:
- Analytical Thinking: Exceptional capability to dissect complex datasets, identify clinical data elements, map system schemas, and produce actionable integration recommendations.
- Interpersonal & Communication: Stellar verbal and written communication skills with a proven ability to explain deep technical integrations to business stakeholders, and complex business workflows to developers.
- Business Process Mapping (BPM): Deep proficiency in visual business process mapping, workflow charting, and detailing clinical system integration touchpoints.
- Analytical Toolsets: Advanced experience utilizing data modeling, reporting, and analysis tools (e.g., Excel pivot tables, SQL, Tableau, Power BI, or workflow visualization software).
- Self-Direction: Highly organized, self-motivated, and capable of operating independently to drive projects to completion while maintaining close alignment with core product goals.
Now we need to output HTML fragment with
sections for About the role, Responsibilities, Qualifications, Skills. No Benefits, Pay, Schedule as not present. We must not include any boilerplate like EEO, agency, veterans, etc. Thus final HTML:
About the role
...intro paragraph...
Responsibilities
- Data Flow & Workflow Analysis: Lead the mapping, analysis, and optimization of complex clinical data flows (e.g., orders, discrete results, genomic data) across internal laboratory information systems (LIS) and external EMR/EHR platforms.
- EHR Integration & Onboarding: Partner with primary EHR vendors and healthcare networks to analyze integration capabilities, define connectivity requirements, and support strategic client migration or transition initiatives.
- Industry Standards Advocacy: Keep abreast of emerging healthcare interoperability guidelines, national standards, and regulations (such as HL7, FHIR, JSON APIs, and HIPAA) to ensure digital products remain leading-edge and compliant.
- Adoption & Growth Analytics: Conduct research and utilize analytical tools to monitor how healthcare providers interact with digital connectivity channels; identify factors that drive product adoption, integration speed, and clinical customer engagement.
- Backlog Management & Story Writing: Write highly descriptive features and user stories centered on technical integrations, API requirements, and system interfaces, aligning with the "Definition Ready" and "Definition of Done."
- Agile Collaboration: Guide agile software engineering and interface squads through story refinement, daily standups, and release planning.
- Technical Roadmapping: Support Product Managers in prioritizing and detailing the interoperability product roadmap, using customer-centric design to minimize implementation barriers.
- Stakeholder Alignment: Coordinate cross-functionally with technical writers, data scientists, security experts, and business partners to design highly scalable, highly secure data transmission infrastructures.
- External Partner Liaison: Collaborate with third-party digital health networks, clinical databases, and external technology consultants to build seamless data bridges.
- Best Practices Leadership: Institutionalize best practices for interface implementation and digital product support, helping the organization transition from legacy integration processes to modern, scalable frameworks.
Qualifications
Education Required: Bachelor’s degree in Computer Science, Health Informatics, Information Technology, Business, or a related field. Equivalent, highly relevant work experience can substitute for the degree.
Required Work Experience: Required: 3+ years of digital product analysis, healthcare IT analyst, or interface engineering experience. Required: At least 1–2 years of direct experience working on healthcare interoperability solutions (such as clinical interface engines, laboratory integrations, or EMR/EHR interfaces).
Preferred Work Experience: Demonstrated success handling complex client-facing software migrations or vendor integrations. Hands-on experience working directly with major EMR/EHR platforms (e.g., Epic, Cerner, OncoEMR) and digital health integration networks. Experience navigating clinical lab networks or specialty diagnostic platforms (e.g., Precision Oncology, Pathology workflows).
Knowledge & Technical Expertise: Standards & Protocols:
- . Probably better to keep as plain text. Thus we will create