L&M Consulting Group
Delivery

Selected healthcare integration work.

Examples from Joey Bartlett's integration, migration, validation, and production-support work. Client names are withheld for confidentiality.

200+ connections
Corepoint rollout and stabilization

Interface operations at scale.

Implemented a Corepoint environment supporting more than 200 connections, then added monitoring, runbooks, change control, and staff training for stable support after handoff.

Multi-million records
FHIR platform migration

FHIR migration and validation at scale.

Migrated multi-million-record Epic datasets between FHIR platforms using repeatable extraction, transformation, and validation workflows.

Daily archive delivery
High-volume HL7 archiving

High-volume HL7 archive delivery.

Designed daily workflows to compress, package, and deliver multi-million-message HL7 archives to client-specific AWS S3 destinations.

Pre-cutover validation
Epic conversions and release validation

Validation before cutover.

Built and maintained interfaces for ADT, laboratory, imaging, vital-sign, and clinical-note conversions, with specifications and unit, system, and integrated testing before cutover.

Additional work includes quarterly Epic release validation and interfaces for immunization reporting, syndromic surveillance, and CCD exchange.

Technical capabilities

Experience across the exchange stack.

EHR systemsEpic, MEDITECH, Cerner, athenahealth, eClinicalWorks, and Allscripts
Interface enginesCorepoint, OPENLink, Mirth, and related middleware
StandardsHL7 v2/v3, FHIR R4, CCD/C-CDA, X12, and CDA
ArchitectureREST, SOAP, JSON, XML, SQL Server, SFTP, VPN, cloud, identity, and high availability
Integration modulesEpic Bridges, MEDITECH NMI, and Cerner FSI
Data transformation and validationMapping, schema transformation, validation, and data-quality workflows
Applied AI

AI-assisted mapping, validation, and analysis.

L&M uses AI to assist with schema transformations, HL7-to-FHIR mappings, validation rules, and technical research. Domain experts set the constraints, test the output, and approve what is used.

Security and privacy follow the engagement

AI tool and data use follow the engagement's security, privacy, and access requirements. Protected or confidential data is not placed in unapproved systems.

EvidenceBegin with source data, domain constraints, and a defined decision.
VerificationKeep outputs inspectable, testable, and subject to qualified review.
HandoffInclude documentation, failure handling, and ownership in the workflow.
Public tools

Public interoperability tools.

HL7Tools.io

Tools built to make HL7 and FHIR messaging more transparent, testable, and developer-friendly.

Visit HL7Tools

Deidentify FHIR

Example tooling for removing or replacing identifying values in FHIR resources. It does not certify HIPAA compliance; each implementation still requires privacy and security review.

View repository

Working on a similar integration problem?

Tell us which systems, migration, or production issue you need to address.