Senior Data Migration Architect - Oracle Health
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the job description and extract sections.
We have:
- Job Description (intro paragraph) describing role: "The Senior Data Migration Architect is a senior-level consulting professional responsible for leading the design, planning, execution, and governance of complex healthcare data migration initiatives supporting Oracle Health Millennium EHR/EMR implementations. This role partners with clients and project teams to migrate clinical, financial, and operational data from legacy systems into Oracle Health solutions, ensuring data integrity, quality, and successful project delivery. As a recognized subject matter expert, the Senior Data Migration Architect provides technical leadership across migration engagements, establishes best practices and standards, resolves complex migration challenges, and serves as the final escalation point for critical migration issues. The role requires independent judgment, strong consulting skills, and expertise in healthcare data migration methodologies, project leadership, and stakeholder management."
That could be "About the role" or "Overview". We'll use
About the role
with containing that paragraph.
- Preferred Qualifications: list bullet points: Experience with Oracle Health Millennium/Cerner solutions. Knowledge of healthcare interoperability standards and clinical data structures. Experience with Oracle databases, SQL, cloud technologies, and data migration automation tools. Experience leading geographically distributed teams and enterprise-scale healthcare projects. Project Management, Healthcare IT, or Data Management certifications.
We could put under "Preferred Qualifications" heading.
- Success Measures: list bullet points: Successful delivery of complex migration projects on time and within budget. High levels of data quality, accuracy, and customer satisfaction. Effective management of project risks, dependencies, and stakeholder expectations. Adoption of migration standards and best practices across engagements. Development and mentorship of migration team members. Achievement of implementation and go-live objectives with minimal migration-related issues.
Could be under "Success Measures" but we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The list includes "Qualifications" and "Skills". We can put Preferred Qualifications under "Qualifications". Success Measures maybe under "Requirements"? Actually "Requirements" is for required qualifications. But we have "Required Qualifications" later. So we can treat "Success Measures" as maybe part of "About the role" or separate? The instruction says include a section only when posting has real specific content for it; we can create sections for "Responsibilities", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We have content for Responsibilities (multiple sub-sections). We have Required Qualifications. We have Preferred Qualifications (maybe also under Qualifications). We have Benefits (detailed). We have Pay (range). We have Travel (maybe under Responsibilities? but we have a Travel line: "Travel: May require travel to customer sites based on project and implementation needs." Could be under Responsibilities or maybe a separate "Schedule"? Travel is not schedule. Could be under Responsibilities as a bullet.
We have no explicit schedule info (like work hours). So we should not create Schedule section if no specific content.
We have Pay: "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $71,200 - $166,100 per year. May be eligible for bonus and equity." That's pay info.
We have Benefits: extensive list.
We have Responsibilities: multiple bullet groups.
We have Required Qualifications: list.
We have Preferred Qualifications: list.
We have Success Measures: maybe could be under "About the role" or "Responsibilities"? But we can include as a separate section maybe "Performance Expectations"? Not allowed headings. Could incorporate into "About the role" or "Responsibilities". Since we prefer few substantive sections, we could merge Success Measures into About the role or Responsibilities. But the instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. That's five sections.
We need to include all substantive info. Let's see if we can fit everything.
About the role: include intro paragraph plus maybe Success Measures? Could add success measures as a bullet list under About the role? But About the role is prose; we can include a
- for success measures? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So if we have a list, we need to use ul/li. So we could have About the role with a
for intro, then a
- for success measures. That's okay.
Responsibilities: we have many sub-sections; we can combine into a single ul list of responsibilities (maybe grouping). But we need to preserve all details. Could break into subheadings? Not allowed to create new headings beyond the allowed list. So we can just have a big ul list with each responsibility as li. That preserves details.
Qualifications: we have Required Qualifications and Preferred Qualifications. Could combine into one ul list, maybe differentiate with text? Could have two separate ul lists under same heading? That's okay. We'll have
Qualifications
then maybe a for required, then ul, then a
for preferred, then ul.
Skills: we could extract skills from responsibilities and qualifications? But we may not need separate Skills section if we already have Qualifications covering skills. The instruction says prefer few substantive sections; we could omit Skills if not needed. However we have explicit skill mentions: "Strong expertise in data extraction, transformation, loading (ETL), data mapping, normalization, and validation methodologies." etc. Those are qualifications. So we can skip Skills.
Benefits: we have a detailed list. We'll create Benefits section with ul.
Pay: we have pay range. We'll create Pay section with p.
Schedule: no specific schedule info, so omit.
Travel: we could include under Responsibilities as a li.
Now need to remove boilerplate: navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove "Qualifications Disclaimer: Certain U.S. based..." etc. Also remove "The role will generally accept applications..." etc. Also remove "About Us" and "Only Oracle brings together..." etc. Also remove "Oracle is an Equal Employment Opportunity Employer." etc. Also remove "Accommodations to this requirement may be granted..." etc. Also remove "As part of Oracle's onboarding process..." etc. Also remove "Only Oracle brings together..." etc. Also remove "Discover your potential..." etc. Also remove "True innovation starts..." etc. Also remove "We’re committed to growing a workforce..." etc. Also remove "We also encourage employees to give back..." etc. Also remove "We’re committed to including people with disabilities..." etc. Also remove "If you require accessibility assistance..." etc. Also remove "Oracle is an Equal Employment Opportunity Employer..." etc. Also remove "Oracle will consider for employment qualified applicants with arrest and conviction records..." etc.
Also remove "Range and benefit information provided in this posting are specific to the stated locations only US:" maybe keep the pay range but remove the sentence about "Range and benefit information provided in this posting are specific to the stated locations only US:"? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The sentence "Range and benefit information provided in this posting are specific to the stated locations only US:" is substantive? It's basically a qualifier that the range applies to US locations. That's substantive. We could keep it as part of Pay section.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
Intro paragraph.
- Success measure 1
...
Responsibilities
- ...
...
Qualifications
Required Qualifications:
- ...
...
Preferred Qualifications:
- ...
...
Benefits
- ...
...
Pay
Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $71,200 - $166,100 per year. May be eligible for bonus and equity.
We need to ensure we didn't miss any substantive info: Travel line, maybe include under Responsibilities.
Also note that the intro paragraph includes "The Senior Data Migration Architect is a senior-level consulting professional responsible for leading the design, planning, execution, and governance of complex healthcare data migration initiatives supporting Oracle Health Millennium EHR/EMR implementations. This role partners with clients and project teams to migrate clinical, financial, and operational data from legacy systems into Oracle Health solutions, ensuring data integrity, quality, and successful project delivery. As a recognized subject matter expert, the Senior Data Migration Architect provides technical leadership across migration engagements, establishes best practices and standards, resolves complex migration challenges, and serves as the final escalation point for critical migration issues. The role requires independent judgment, strong consulting skills, and expertise in healthcare data migration methodologies, project leadership, and stakeholder management."
We'll put that as .
Success Measures list: we need to capture each bullet:
- Successful delivery of complex migration projects on time and within budget.
- High levels of data quality, accuracy, and customer satisfaction.
- Effective management of project risks, dependencies, and stakeholder expectations.
- Adoption of migration standards and best practices across engagements.
- Development and mentorship of migration team members.
- Achievement of implementation and go-live objectives with minimal migration-related issues.
We'll put those as li under About the role after intro.
Responsibilities: we have many bullet groups under headings: Data Migration Strategy & Leadership, Solution Design & Implementation, Technical Expertise & Problem Resolution, Project & Stakeholder Management, Standards, Governance & Process Improvement, Team Development & Mentorship, Business Development & Organizational Contribution, plus Travel line.
We need to extract each bullet point.
Let's list them:
Data Migration Strategy & Leadership:
- Lead the design, planning, and execution of complex data migration projects for Oracle Health implementations.
- Define migration strategies, scope, requirements, timelines, and deliverables based on customer business and technical objectives.
- Develop and oversee comprehensive migration plans, ensuring alignment with project goals, budgets, and implementation schedules.
- Serve as the primary migration lead and trusted advisor for clients and project stakeholders.
Solution Design & Implementation:
- Lead complex migration build design and large-scale data upload activities.
- Design data extraction, transformation, mapping, normalization, validation, and loading solutions.
- Ensure migration solutions meet Oracle Health standards, methodologies, and leading industry practices.
- Drive the successful delivery of integrated technical and functional migration solutions.
Technical Expertise & Problem Resolution:
- Serve as the final escalation point for migration-related issues identified during testing, validation, and production migration activities.
- Identify, diagnose, and resolve complex technical and data quality challenges.
- Provide expert guidance on healthcare data structures, conversion methodologies, and migration best practices.
- Evaluate risks and implement mitigation strategies to ensure successful migration outcomes.
Project & Stakeholder Management:
- Oversee the successful completion of migration projects, including resource coordination, task delegation, dependency management, and risk tracking.
- Manage communication with project
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the job description and extract sections. We have: - Job Description (intro paragraph) describing role: "The Senior Data Migration Architect is a senior-level consulting professional responsible for leading the design, planning, execution, and governance of complex healthcare data migration initiatives supporting Oracle Health Millennium EHR/EMR implementations. This role partners with clients and project teams to migrate clinical, financial, and operational data from legacy systems into Oracle Health solutions, ensuring data integrity, quality, and successful project delivery. As a recognized subject matter expert, the Senior Data Migration Architect provides technical leadership across migration engagements, establishes best practices and standards, resolves complex migration challenges, and serves as the final escalation point for critical migration issues. The role requires independent judgment, strong consulting skills, and expertise in healthcare data migration methodologies, project leadership, and stakeholder management." That could be "About the role" or "Overview". We'll use
About the role
withcontaining that paragraph. - Preferred Qualifications: list bullet points: Experience with Oracle Health Millennium/Cerner solutions. Knowledge of healthcare interoperability standards and clinical data structures. Experience with Oracle databases, SQL, cloud technologies, and data migration automation tools. Experience leading geographically distributed teams and enterprise-scale healthcare projects. Project Management, Healthcare IT, or Data Management certifications. We could put under "Preferred Qualifications" heading. - Success Measures: list bullet points: Successful delivery of complex migration projects on time and within budget. High levels of data quality, accuracy, and customer satisfaction. Effective management of project risks, dependencies, and stakeholder expectations. Adoption of migration standards and best practices across engagements. Development and mentorship of migration team members. Achievement of implementation and go-live objectives with minimal migration-related issues. Could be under "Success Measures" but we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The list includes "Qualifications" and "Skills". We can put Preferred Qualifications under "Qualifications". Success Measures maybe under "Requirements"? Actually "Requirements" is for required qualifications. But we have "Required Qualifications" later. So we can treat "Success Measures" as maybe part of "About the role" or separate? The instruction says include a section only when posting has real specific content for it; we can create sections for "Responsibilities", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We have content for Responsibilities (multiple sub-sections). We have Required Qualifications. We have Preferred Qualifications (maybe also under Qualifications). We have Benefits (detailed). We have Pay (range). We have Travel (maybe under Responsibilities? but we have a Travel line: "Travel: May require travel to customer sites based on project and implementation needs." Could be under Responsibilities or maybe a separate "Schedule"? Travel is not schedule. Could be under Responsibilities as a bullet. We have no explicit schedule info (like work hours). So we should not create Schedule section if no specific content. We have Pay: "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $71,200 - $166,100 per year. May be eligible for bonus and equity." That's pay info. We have Benefits: extensive list. We have Responsibilities: multiple bullet groups. We have Required Qualifications: list. We have Preferred Qualifications: list. We have Success Measures: maybe could be under "About the role" or "Responsibilities"? But we can include as a separate section maybe "Performance Expectations"? Not allowed headings. Could incorporate into "About the role" or "Responsibilities". Since we prefer few substantive sections, we could merge Success Measures into About the role or Responsibilities. But the instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. That's five sections. We need to include all substantive info. Let's see if we can fit everything. About the role: include intro paragraph plus maybe Success Measures? Could add success measures as a bullet list under About the role? But About the role is prose; we can include a
- for success measures? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So if we have a list, we need to use ul/li. So we could have About the role with a
for intro, then a
- for success measures. That's okay.
Responsibilities: we have many sub-sections; we can combine into a single ul list of responsibilities (maybe grouping). But we need to preserve all details. Could break into subheadings? Not allowed to create new headings beyond the allowed list. So we can just have a big ul list with each responsibility as li. That preserves details.
Qualifications: we have Required Qualifications and Preferred Qualifications. Could combine into one ul list, maybe differentiate with text? Could have two separate ul lists under same heading? That's okay. We'll have
Qualifications
then maybe afor required, then ul, then a
for preferred, then ul. Skills: we could extract skills from responsibilities and qualifications? But we may not need separate Skills section if we already have Qualifications covering skills. The instruction says prefer few substantive sections; we could omit Skills if not needed. However we have explicit skill mentions: "Strong expertise in data extraction, transformation, loading (ETL), data mapping, normalization, and validation methodologies." etc. Those are qualifications. So we can skip Skills. Benefits: we have a detailed list. We'll create Benefits section with ul. Pay: we have pay range. We'll create Pay section with p. Schedule: no specific schedule info, so omit. Travel: we could include under Responsibilities as a li. Now need to remove boilerplate: navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove "Qualifications Disclaimer: Certain U.S. based..." etc. Also remove "The role will generally accept applications..." etc. Also remove "About Us" and "Only Oracle brings together..." etc. Also remove "Oracle is an Equal Employment Opportunity Employer." etc. Also remove "Accommodations to this requirement may be granted..." etc. Also remove "As part of Oracle's onboarding process..." etc. Also remove "Only Oracle brings together..." etc. Also remove "Discover your potential..." etc. Also remove "True innovation starts..." etc. Also remove "We’re committed to growing a workforce..." etc. Also remove "We also encourage employees to give back..." etc. Also remove "We’re committed to including people with disabilities..." etc. Also remove "If you require accessibility assistance..." etc. Also remove "Oracle is an Equal Employment Opportunity Employer..." etc. Also remove "Oracle will consider for employment qualified applicants with arrest and conviction records..." etc. Also remove "Range and benefit information provided in this posting are specific to the stated locations only US:" maybe keep the pay range but remove the sentence about "Range and benefit information provided in this posting are specific to the stated locations only US:"? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The sentence "Range and benefit information provided in this posting are specific to the stated locations only US:" is substantive? It's basically a qualifier that the range applies to US locations. That's substantive. We could keep it as part of Pay section. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:
About the role
Intro paragraph.
- Success measure 1 ...
Responsibilities
- ... ...
Qualifications
Required Qualifications:
- ... ...
Preferred Qualifications:
- ... ...
Benefits
- ... ...
Pay
Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $71,200 - $166,100 per year. May be eligible for bonus and equity.
We need to ensure we didn't miss any substantive info: Travel line, maybe include under Responsibilities. Also note that the intro paragraph includes "The Senior Data Migration Architect is a senior-level consulting professional responsible for leading the design, planning, execution, and governance of complex healthcare data migration initiatives supporting Oracle Health Millennium EHR/EMR implementations. This role partners with clients and project teams to migrate clinical, financial, and operational data from legacy systems into Oracle Health solutions, ensuring data integrity, quality, and successful project delivery. As a recognized subject matter expert, the Senior Data Migration Architect provides technical leadership across migration engagements, establishes best practices and standards, resolves complex migration challenges, and serves as the final escalation point for critical migration issues. The role requires independent judgment, strong consulting skills, and expertise in healthcare data migration methodologies, project leadership, and stakeholder management." We'll put that as. Success Measures list: we need to capture each bullet: - Successful delivery of complex migration projects on time and within budget. - High levels of data quality, accuracy, and customer satisfaction. - Effective management of project risks, dependencies, and stakeholder expectations. - Adoption of migration standards and best practices across engagements. - Development and mentorship of migration team members. - Achievement of implementation and go-live objectives with minimal migration-related issues. We'll put those as li under About the role after intro. Responsibilities: we have many bullet groups under headings: Data Migration Strategy & Leadership, Solution Design & Implementation, Technical Expertise & Problem Resolution, Project & Stakeholder Management, Standards, Governance & Process Improvement, Team Development & Mentorship, Business Development & Organizational Contribution, plus Travel line. We need to extract each bullet point. Let's list them: Data Migration Strategy & Leadership: - Lead the design, planning, and execution of complex data migration projects for Oracle Health implementations. - Define migration strategies, scope, requirements, timelines, and deliverables based on customer business and technical objectives. - Develop and oversee comprehensive migration plans, ensuring alignment with project goals, budgets, and implementation schedules. - Serve as the primary migration lead and trusted advisor for clients and project stakeholders. Solution Design & Implementation: - Lead complex migration build design and large-scale data upload activities. - Design data extraction, transformation, mapping, normalization, validation, and loading solutions. - Ensure migration solutions meet Oracle Health standards, methodologies, and leading industry practices. - Drive the successful delivery of integrated technical and functional migration solutions. Technical Expertise & Problem Resolution: - Serve as the final escalation point for migration-related issues identified during testing, validation, and production migration activities. - Identify, diagnose, and resolve complex technical and data quality challenges. - Provide expert guidance on healthcare data structures, conversion methodologies, and migration best practices. - Evaluate risks and implement mitigation strategies to ensure successful migration outcomes. Project & Stakeholder Management: - Oversee the successful completion of migration projects, including resource coordination, task delegation, dependency management, and risk tracking. - Manage communication with project
- for success measures. That's okay.
Responsibilities: we have many sub-sections; we can combine into a single ul list of responsibilities (maybe grouping). But we need to preserve all details. Could break into subheadings? Not allowed to create new headings beyond the allowed list. So we can just have a big ul list with each responsibility as li. That preserves details.
Qualifications: we have Required Qualifications and Preferred Qualifications. Could combine into one ul list, maybe differentiate with text? Could have two separate ul lists under same heading? That's okay. We'll have
- for any list of duties/requirements/benefits, and