ModMed EMA

Available on request
HIPAA-readyWe sign a Business Associate Agreement
Pricing
Connected plan Quoted on the scoping call.
Patient data
Uses patient data
Developer
Velarya
What syncs once builtInto Velarya
  • Patient name, email, phone and birthdayPatient data

    In ModMed EMAPatient demographics

    In VelaryaMember profile

  • Completed visit date, type and locationPatient data

    In ModMed EMAAppointment or encounter status

    In VelaryaVisit points

  • Location list

    In ModMed EMAPractice locations set up in ModMed EMA

    In VelaryaLocation mapping

Visit points from completed ModMed EMA visits, with the chart left in ModMed

Available on request. Our team builds the ModMed EMA connection for your practice after a scoping call. Once we build it for your practice, completed visits in ModMed EMA award points in Velarya, and patients become Velarya members with the contact details the app needs. The connection reads schedule and demographic data only, so the chart stays in ModMed. We choose between ModMed's read-only FHIR API and its EMA Proprietary API on the scoping call.

  • Award visit points when a ModMed EMA visit is completed
  • Create and update members from ModMed patient demographics
  • Count only the visit types you choose, such as cosmetic visits
  • Map each ModMed location to its Velarya location
Works with
Points, Member profiles
Relevant for

Dermatology

How it works

Available on request. Book a call, we scope it against ModMed EMA's published API, build and test it with your team, and it goes live in your account.

  1. On the scoping call we choose the route: ModMed's read-only FHIR API or the EMA Proprietary API.

  2. For the FHIR route, your practice admin adds Velarya's client ID in ModMed once.

  3. For the proprietary route, we build in ModMed's sandbox and complete its technical review first.

  4. The connection reads completed visits and patient contact details, then awards points in Velarya.

Each connection is scoped on a call and quoted separately, and the timeline is agreed on that call.

Questions

About the ModMed EMA connection

Does Velarya integrate with ModMed EMA?

Available on request: our team builds the connection for your practice after a scoping call, using ModMed's published APIs. It awards points for completed visits and leaves the chart in ModMed.

Does Velarya see our patients' charts?

The build reads patient contact details and completed visits, which is what points and member profiles need. Diagnoses, notes, photos and the rest of the chart stay in ModMed EMA.

Which ModMed route will you use?

ModMed's FHIR API is read-only and needs a one-time step from your practice admin. The EMA Proprietary API goes through ModMed's synapSYS technical review first. We recommend one on the scoping call, based on what you want points for.

Can points go to cosmetic visits only?

Yes. We agree on the scoping call which ModMed visit types count, so you can award points on cosmetic visits and leave medical visits out. If you bill federal programs, talk to your counsel about patient incentives.

What does our ModMed admin need to do?

For the FHIR route, add Velarya's client ID to your practice once in ModMed. For the proprietary route, tell your ModMed account manager you want Velarya connected once ModMed's technical review of the build is complete.

Support

Our team builds and supports this connection.

Patient data

Patient demographics and visit dates from an electronic health record are protected health information, so Velarya signs a Business Associate Agreement with your practice before data flows. The connection asks for the narrowest access ModMed offers for demographics and visits; diagnoses, notes and images stay in ModMed. We confirm ModMed's terms for patient data on the scoping call.

See how we protect patient data.

Requirements

On our side: the Connected plan.

About ModMed EMA

ModMed, from Modernizing Medicine, Inc., makes specialty software including the EMA electronic health record used by dermatology practices. Its API portal documents a read-only FHIR API and the EMA Proprietary API.

Trademarks

ModMed and EMA are trademarks of Modernizing Medicine, Inc. Velarya is independent of Modernizing Medicine, Inc. and is not affiliated with, sponsored by or endorsed by Modernizing Medicine, Inc.

The logo shown for ModMed EMA belongs to Modernizing Medicine, Inc. and appears here only to identify its product.

Want the ModMed EMA connection for your practice?

Book a call. We scope the ModMed EMA connection against ModMed EMA's published API and agree the timeline with your team.

Request this integration