PFH Technology
Lead Integration & Interoperability Architect
Dublin 2, Dublin
hirly Pro
Get in front of the people hiring at PFH Technology
- Reach the hiring manager at PFH Technology on LinkedIn, from your own account
- hirly applies to this job for you, with unlimited applications
- A resume and cover letter written for this job, unlimited
- The hiring manager and recruiter at PFH Technology, with contact details
$49 a month · ₹1,999 for 30 days in India · cancel any time
Get past the screening software and onto a recruiter's desk
hirly rewrites your resume for this job — matching the keywords and skills in the posting, moving your most relevant experience to the top, and writing a cover letter to fit. About 30 seconds.
- Keywords matched to this posting
- Fit score before you apply
- Cover letter included
Matched against 2.8M live jobs from 220,000+ employers in 200+ countries.
Tailor my resume for this job →Apply from your AI assistant
Connect hirly to Claude or ChatGPT and ask it to apply to this job. hirly tailors your resume, fills the employer’s form and asks before sending.
Some employer sites stop an application at a CAPTCHA or sign-in and hand it back with a link. Applying needs a paid plan. Works with any assistant that supports MCP.
hirly's read of this role
- Seniority
- Lead / management
- Country
- IE
- Work mode
- On-site / unstated
- First seen by hirly
- 11 Nov 2026
Derived automatically from the posting. Upload your resume above to see how the role scores against it.
the posting
The Lead Integration & Interoperability Architect will provide strategic and hands-on architectural leadership for the HSE Shared Care Record integration capability and its associated healthcare data platform. The role is accountable for defining how data is received, validated, transformed, standardised, governed and made available to the Shared Care Record (SCR) platform, which is based on the Better EHR platform, and to other approved national services.
The integration estate will receive data from a wide range of clinical, administrative and operational systems using heterogeneous formats and protocols. These may include HL7 v2 and v3 messages, HL7 FHIR, openEHR, JSON, XML, CSV and other file-based or API-based exchanges. The architect will establish the patterns, standards and governance required to convert these inputs into consistent, reusable and clinically meaningful target representations.
The role will have particular responsibility for the integration and ingestion layers that connect source systems to the SCR platform, while providing architectural oversight across the wider transformation, standardisation and consumption capabilities. The architect must ensure that decisions made at the point of ingestion support downstream clinical modelling, data quality, operational use, analytics and future reuse.
The post holder must be able to work across technology, data, clinical informatics and business domains at both enterprise and detailed solution level. The role will engage with source-system owners, programme teams, clinical stakeholders, data engineers, integration developers, technology teams, information governance, cyber security, suppliers and the SCR platform provider.
Key Responsibilities
1. Integration and Interoperability Architecture
Lead the creation, evolution and implementation of the HSE Shared Care Record integration and interoperability architecture.
Define the end-to-end integration architecture from source-system connectivity through ingestion, transformation, standardisation and publishing to the SCR platform.
Develop reusable integration patterns for messaging, APIs, events, files, batch transfers and near-real-time data exchange.
Define when Rhapsody, data engineering services, APIs, event-driven components or other platform capabilities should be used, and establish clear responsibility boundaries between them.
Ensure architecture decisions support national-scale performance, resilience, security, operability and future extensibility.
Provide architecture leadership for complex integrations spanning multiple organisations, vendors, care settings and technology platforms.
2. Rhapsody and Integration-Layer Ownership
Own the architecture of the core integration and ingestion layers, including connectivity, routing, message handling, validation, enrichment, persistence, replay and failure management.
Define Rhapsody implementation standards, route patterns, component reuse, configuration conventions, deployment practices and environment management.
Establish patterns for receiving HL7, FHIR, JSON, XML, CSV and other structured or semi-structured data.
Define source onboarding standards covering interface contracts, connectivity, security, message profiles, test evidence, operational readiness and support ownership.
Ensure raw-source fidelity, provenance, traceability and auditability are retained so that data can be reprocessed when mappings, rules or target models change.
Provide design assurance and technical direction to Rhapsody developers, integration engineers and supplier teams.
3. Integration, Transformation and Data Standardisation Architecture
Define the architectural responsibilities, entry and exit criteria, data contracts and quality controls across the ingestion, transformation, standardisation and consumption layers.
Ensure the integration layer preserves source data and technical metadata while providing controlled validation and quarantine of invalid or incomplete records.
Define the approach for cleansing, deduplication, terminology normalisation, identity resolution, canonicalisation and conformance to approved clinical models.
Define the approach for producing trusted, consumable datasets and services supporting the SCR, clinical, operational, reporting and approved secondary-use requirements.
Prevent duplication or ambiguity between integration-engine transformations and downstream data-processing and standardisation activities.
Establish lineage and reconciliation controls allowing records to be traced from source payload through each transformation stage to the final target representation.
4. Healthcare Standards and Clinical Modelling
Lead the application of healthcare messaging and interoperability standards, including HL7 v2, HL7 v3, HL7 FHIR, IHE profiles and openEHR.
Define the approach for translating local and vendor-specific source formats into standardised FHIR resources and openEHR archetypes/templates used by the SCR platform.
Oversee the development and governance of message profiles, FHIR profiles, implementation guides, openEHR templates, canonical models and mapping specifications.
Ensure semantic interoperability through appropriate use of terminology standards such as SNOMED CT, LOINC, ICD and approved national code systems.
Work with clinical informatics and terminology specialists to ensure transformations preserve clinical meaning, context, units, status, provenance and interpretive information.
Define versioning, backward compatibility and migration approaches for standards, profiles, archetypes, mappings and interface contracts.
Provide architectural leadership on alignment with the European Health Data Space (EHDS), including implications for primary use, secondary use, cross-border exchange, interoperability and data portability.
Ensure integration and data-standardisation approaches are capable of supporting European Electronic Health Record exchange requirements and future European interoperability specifications.
Assess the impact of EHDS requirements on data formats, metadata, provenance, consent, access controls, auditability, patient access and permitted reuse of health data.
Work with policy, legal, clinical, data-governance and programme stakeholders to translate EHDS obligations into practical architecture principles, standards, controls and delivery roadmaps.
5. Data Quality, Validation and Transformation
Define layered validation covering transport, syntax, structure, conformance, terminology, business rules and clinical plausibility.
Establish consistent error-handling patterns, including rejection, quarantine, correction, replay, alerting and escalation.
Define data-quality metrics and thresholds for completeness, accuracy, timeliness, uniqueness, consistency and conformance.
Ensure transformation logic is documented, testable, version controlled and subject to appropriate clinical and architecture approval.
Establish reconciliation controls between source-system volumes, ingestion outcomes, transformed records and records accepted by the SCR platform.
Support the design of data correction and remediation processes without compromising source fidelity or audit history.
6. API, Messaging and Event-Driven Integration
Define secure and reusable API-led integration patterns, including RESTful APIs, FHIR APIs, asynchronous messaging and event-driven integration.
Define interface contract standards covering schemas, profiles, error models, idempotency, correlation, pagination, versioning and service-level expectations.
Establish patterns for synchronous and asynchronous processing, guaranteed delivery, retries, dead-letter handling, duplicate detection and ordering.
Ensure integration solutions are loosely coupled and avoid unnecessary point-to-point dependencies.
Align integration patterns with wider enterprise API management, messaging, id
Listed on hirly, a job board. hirly is not the employer: PFH Technology is hiring for this role.
Browse similar roles
Want this one?
Upload your resume and hirly rewrites it for this job and writes the cover letter — in about thirty seconds, before you sign up.
Tailor my resume for this job