Create a TEFCA-CommonWell organization record

Last updated: Apr 14, 2026
IMPLEMENTATION
DEVELOPER
Coming soon

This feature is coming soon, so you won’t see it live in a production environment just yet. Stay tuned for the release!

Who can use this how-to
  • Existing customers using Network Onramps to connect to TEFCA via CommonWell

An organization record (i.e., OID in the Redox organization) is the unique identifier for your organization within the CommonWell Health Alliance. The organization OID is how you identify yourself when searching for patients—and how other TEFCA-CommonWell participants can find you and your patients.

You should plan to register at least one organization record per unique master patient index (MPI) or physical location. Learn more about OIDs and identity to understand why you may want to register more than one organization.

Use curl for technical validation

You can copy our code examples and send the test requests with curl (learn more about curl) instead of Postman. If you do, remember to:

  • Remove the comments from the code examples (starting with //).
  • Replace any variables (e.g., {{variable here}}).
  • Add the source-id if you have multiple sources. We don’t include {{source-id}} in the code examples, so you’ll have to add them yourself. Learn about including source details.
  • Make sure you have a full request for your own use since some of the code examples are abbreviated.

Check out these troubleshooting guides if you run into errors:

Create your organization record

  1. In your staging environment, using Postman or curl, send an Organization.New request to create your organization record in TEFCA-CommonWell.
    Example: Create a TEFCA-CommonWell organization record
    bash
    1
    curl \
    2
    -X POST https://api.redoxengine.com/endpoint \
    3
    -H "Content-Type: application/json" \
    4
    -H "Authorization: Bearer $API_TOKEN" \
    5
    -d '{
    6
    "Meta": {
    7
    "DataModel": "Organization",
    8
    "EventType": "New",
    9
    "Destinations": [
    10
    {
    11
    "ID": "3122bfff-f1fb-4fdf-97de-294f24338229",
    12
    "Name": "CommonWell EMPI [Integration]"
    13
    }
    14
    ]
    15
    },
    16
    "Directory": "CommonWell",
    17
    "Action": "Create",
    18
    "Organizations": [
    19
    {
    20
    "Name": "My Company",
    21
    "Aliases": ["My Company, LLC", "MY"],
    22
    "Active": true,
    23
    24
    "Identifiers": [
    25
    {
    26
    // OID is your organization's ID .
    27
    "ID": "{{your-OID}}",
    28
    "IDType": "OID"
    29
    },
    30
    {
    31
    // Your PIAA is your patient identifier assigning authority.
    32
    // Your IDs will be scoped under this and show up as an 'IDType' in patient / document queries.
    33
    "ID": "{{your-PIAA}}",
    34
    "IDType": "PIAA"
    35
    },
    36
    {
    37
    // TEFCA requires that at last one of [TIN, NPI Type 1 or NPI Type 2] to be assigned to
    38
    each org. However, include all that are applicable.
    39
    "ID": "{{your-npitype1}}",
    40
    "IDType": "NPI Type 1"
    41
    },
    42
    {
    43
    // TEFCA requires that at last one of [TIN, NPI Type 1 or NPI Type 2] to be assigned to
    44
    each org. However, include all that are applicable.
    45
    "ID": "{{your-npitype2}}",
    46
    "IDType": "NPI Type 2"
    47
    },
    48
    {
    49
    // TEFCA requires that at last one of [TIN, NPI Type 1 or NPI Type 2] to be assigned to
    50
    each org. However, include all that are applicable.
    51
    "ID": "{{your-tin}}",
    52
    "IDType": "Tax Identification Number"
    53
    },
    54
    ],
    55
    // This references Redox as your top-level, and your other organizations for levels below.
    56
    "PartOf": {
    57
    "Identifier": {
    58
    // Your "PartOf" or parent should be Redox: 2.16.840.1.113883.3.6147.458.2
    59
    "Value": "{{your-base-OID}}"
    60
    }
    61
    },
    62
    // Replace this information with your contact information.
    63
    "Contacts": [
    64
    {
    65
    "Purpose": "Technical",
    66
    "Name": "Redox CommonWell Support - Test",
    67
    "EmailAddresses": ["support@redoxengine.com"],
    68
    "PhoneNumber": {
    69
    "Work": "+16085359501",
    70
    "Mobile": "+16085359501"
    71
    }
    72
    }
    73
    ],
    74
    // Replace this information with your address information.
    75
    "Address": {
    76
    "StreetAddress": "2020 Eastwood Dr",
    77
    "City": "Madison",
    78
    "State": "WI",
    79
    "ZIP": "53704",
    80
    "County": "Dane",
    81
    "Country": "USA"
    82
    }
    83
    }
    84
    ]
    85
    }'
    API reference

    Review the Organization data model schema for more technical details.

  2. If the request is successful, you receive a synchronous response indicating that your organization record was created.
    Example: Successful response for new TEFCA-CommonWell organization record
    json
    1
    {
    2
    "Meta": {
    3
    "DataModel": "Organization",
    4
    "EventType": "New",
    5
    "Message": {
    6
    "ID": 4606153124
    7
    },
    8
    "Source": {
    9
    "ID": "7f296bb4-83fd-498d-92f3-a76960648788",
    10
    },
    11
    "Destinations": [
    12
    {
    13
    "ID": "a07afe3b-d247-4415-827f-6837707e1b8b"
    14
    }
    15
    ],
    16
    "Extensions": {
    17
    "ResponseDetail": {
    18
    "string": "New organization was added successfully."
    19
    }
    20
    }
    21
    }
    22
    }
    Redoxer setup must be done

    Every organization record created in CommonWell-TEFCA must have an associated Data Network Participant Repository (DNPR) setup within Redox. Only a Redoxer can manage your DNPR setup. If you don’t receive the expected response, submit a Help Center request to get help. In the ticket, include your organization OID, your destination ID for document responding, and your supported purpose(s) of use.

    For help with errors, review common TEFCA-CommonWell errors.

  3. Once you complete all of your testing, repeat these steps to create your organization record in production, too.

Maintain your organization record

Whenever there are changes to your organization details (e.g., address or contact information), follow these steps to keep your organization record up-to-date:

  1. Using Postman or curl, send an Organization.Update request with the updated or new organization details.
    Example: Update a TEFCA-CommonWell organization record
    bash
    1
    curl \
    2
    -X POST https://api.redoxengine.com/endpoint \
    3
    -H "Content-Type: application/json" \
    4
    -H "Authorization: Bearer $API_TOKEN" \
    5
    -d ' "Meta": {
    6
    "DataModel": "Organization",
    7
    "EventType": "Update",
    8
    "Destinations": [
    9
    {
    10
    "ID": "3122bfff-f1fb-4fdf-97de-294f24338229",
    11
    "Name": "CommonWell EMPI [Integration]"
    12
    }
    13
    ]
    14
    },
    15
    "Directory": "CommonWell",
    16
    "Action": "Update",
    17
    "Organizations": [
    18
    {
    19
    "Name": "My Company",
    20
    "Aliases": ["My Company, LLC", "MY"],
    21
    "Active": true,
    22
    23
    "Identifiers": [
    24
    {
    25
    // OID is your organization's ID .
    26
    "ID": "{{your-OID}}",
    27
    "IDType": "OID"
    28
    },
    29
    {
    30
    // Your PIAA is your patient identifier assigning authority.
    31
    // Your IDs will be scoped under this and show up as an 'IDType' in patient / document queries.
    32
    "ID": "{{your-PIAA}}",
    33
    "IDType": "PIAA"
    34
    },
    35
    {
    36
    // TEFCA requires that at last one of [TIN, NPI Type 1 or NPI Type 2] to be assigned to
    37
    each org. However, include all that are applicable.
    38
    "ID": "{{your-npitype1}}",
    39
    "IDType": "NPI Type 1"
    40
    },
    41
    {
    42
    // TEFCA requires that at last one of [TIN, NPI Type 1 or NPI Type 2] to be assigned to
    43
    each org. However, include all that are applicable.
    44
    "ID": "{{your-npitype2}}",
    45
    "IDType": "NPI Type 2"
    46
    },
    47
    {
    48
    // TEFCA requires that at last one of [TIN, NPI Type 1 or NPI Type 2] to be assigned to
    49
    each org. However, include all that are applicable.
    50
    "ID": "{{your-tin}}",
    51
    "IDType": "Tax Identification Number"
    52
    },
    53
    ],
    54
    // This references Redox as your top-level, and your other organizations for levels below.
    55
    "PartOf": {
    56
    "Identifier": {
    57
    // Your "PartOf" or parent should be Redox: 2.16.840.1.113883.3.6147.458.2
    58
    "Value": "{{your-base-OID}}"
    59
    }
    60
    },
    61
    // Replace this information with your contact information.
    62
    "Contacts": [
    63
    {
    64
    "Purpose": "Technical",
    65
    "Name": "Redox CommonWell Support - Test",
    66
    "EmailAddresses": ["support@redoxengine.com"],
    67
    "PhoneNumber": {
    68
    "Work": "+16085359501",
    69
    "Mobile": "+16085359501"
    70
    }
    71
    }
    72
    ],
    73
    // Replace this information with your address information.
    74
    "Address": {
    75
    "StreetAddress": "2020 Eastwood Dr",
    76
    "City": "Madison",
    77
    "State": "WI",
    78
    "ZIP": "53704",
    79
    "County": "Dane",
    80
    "Country": "USA"
    81
    }
    82
    }
    83
    ]
    84
    }'
    API reference

    Review the Organization data model schema for more technical details.

  2. If the request is successful, you receive a synchronous response indicating that your organization record was updated.

Next steps

FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.