EMR Architect

KFORCE URGENT REQUIREMENT

Looking for candidates regarding the following:

POSITION

EMR Architect

LOCATION

Remote

DURATION

612 months

PAY RATE

Market rate send best you can

INTERVIEW TYPE

Video

VISA RESTRICTIONS

None

REQUIRED SKILLS

Lead EMR Integration Architect

Required: 10 years of experience: EMR experience Integration Data and API experience leading large implementation for a large company/enterprise like Humana lead experience some ppl management skills and experience Interested in someone with architectural or tech lead experience on Athena (A EMR / electronic medical record system).

They have EMR migration work thats theyre starting up migrating away from a legacy platform to a modern headless platform.

Headless EHRs are APIcentric products that provide patient data management and other provider workflow APIs without necessarily providing a traditional frontend interface.

The main difference between an electronic health record (EHR) and an electronic medical record (EMR) is that EHRs can be shared across multiple healthcare providers while EMRs are limited to a single practice

knowledge of SAAS important

Work with vendors day in and day out.

They need to have a lot of experience in healthcare and EMR.

Primary needs are EMR integration / migration experience in healthcare.

Primarily: Oversee the end to end integration of and migration of EMR systems should be able to design for interfacing REST APIs and oversee data migration activities.

Architect with broad enough experience to understand HL7 and FHIR standards see below for explanation of what they mean

FHIR and HL7 are both healthcare data exchange standards but they differ in their approach development technologies and use cases:

FHIR

Stands for Fast Healthcare Interoperability Resources. FHIR is a modern standard that uses a webbased API approach to exchange data. FHIR is designed to be adaptable to the evolving needs of healthcare systems. Its compatible with mobile devices and webbased platforms and it has stronger security features than HL7. FHIR is used for personal health records clinical decision support and more.

HL7

An international standard that uses structured messages in a pointtopoint communication model. HL7 is used for electronic health records management lab test ordering and global collaboration.

Here are some other differences between FHIR and HL7:

Development technologies

FHIR uses RESTful web services and open web technologies like JSON and RDF data formats.

Integration

FHIR is easier to integrate than HL7.

Interoperability

FHIR improves interoperability between EHR systems mobile apps mobile devices and wearables.

Data exchange

FHIRs API standards streamline data exchange and make it easier to extract contextual information from data sources.

Many healthcare organizations use a hybrid approach that combines the strengths of both FHIR and HL7.

Client: Conviva