Skip to main content
Minnesota Department of Health logo
  • Main navigation

    • Home
    • Data, Statistics, and Legislation
    • Diseases and Conditions
    • Health Care Facilities, Providers, and Insurance
    • Healthy Communities, Environment, and Workplaces
    • Individual and Family Health
    • About Us
    • News and Announcements
    • Translated Materials

Main navigation mobile

  • Data, Statistics, and Legislation
  • Diseases and Conditions
  • Health Care Facilities, Providers, and Insurance
  • Healthy Communities, Environment, and Workplaces
  • Individual and Family Health
  • About Us
  • News and Announcements
  • Translated Materials
MDH Logo

Breadcrumb

  1. Home
  2. Data, Statistics and Legislation
Topic Menu

Integration Services

  • Integration Services Home
  • MDH Data Exchange Gateway (DEX)
    • DEX Portal
    • DEX Owners
    • DEX Config
    • DEX Resources

Integration Services

  • Integration Services Home
  • MDH Data Exchange Gateway (DEX)
    • DEX Portal
    • DEX Owners
    • DEX Config
    • DEX Resources
Contact Info
Integration Services
MDH DEX Help Request Form

Contact Info

Integration Services
MDH DEX Help Request Form

Data Exchange Gateway (DEX) Config

The MDH DEX Config is an internal application that allows MDH DEX administrators to create DEX resource owners and DEX resources.

How to a create a new resource owner

The first step is to create a new AD group that will contain the individuals that will be resource owners. The AD group must be placed under OU=Messaging, OU=Service, OU=NDS, DC=MDH-AD, DC=HEALTH, DC=STATE, DC=MN, DC=US and the AD group name must start with DEX-Owner-.

How to create a new resource

  1. Owner: Select the group responsible to administrator resource access.
  2. Select the scope (GET, POST, PUT)
    1. PUT - should be used with direct resources only since 2025.08.07.
  3. Display Name: Include the owner group name and details regarding the type of message.
    1. Example: MSG - Input - Developer
  4. Access Type: Direct for GET and PUT, Proxy for POST.
  5. Context Path: starting with the owner then go from least to most specific.  This is a bit subjective.
    1. Example: msg/input/developer
  6. Supporting Documentation: Optional.  Add link to owner group website for implementation guides or the DEX Resources subsite when available.
Tags
  • interoperability
Last Updated: 10/02/2025

Get email updates


Minnesota Department of Health logo

Privacy Policy
Equal Opportunity
Translated Materials
Feedback Form
About MDH
Minnesota.gov
  • Facebook
  • Twitter
  • Linked In
  • Instagram
  • Youtube
Minnesota Department of Health Minnesota Department of health print search share facebook instagram linkedin twitter youtube