Skip to content

Commit 2c60c13

Browse files
ecfanecfan
committed
Updates per feedback
1 parent 0c2dd85 commit 2c60c13

File tree

2 files changed

+62
-66
lines changed

2 files changed

+62
-66
lines changed

‎articles/logic-apps/logic-apps-enterprise-integration-x12.md

Lines changed: 62 additions & 66 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: divyaswarnkar
77
ms.author: divswa
88
ms.reviewer: jonfan, estfan, logicappspm
99
ms.topic: article
10-
ms.date: 04/23/2020
10+
ms.date: 04/29/2020
1111
---
1212

1313
# Exchange X12 messages for B2B enterprise integration in Azure Logic Apps with Enterprise Integration Pack
@@ -26,7 +26,7 @@ To work with X12 messages in Azure Logic Apps, you can use the X12 connector, wh
2626

2727
* The [schemas](../logic-apps/logic-apps-enterprise-integration-schemas.md) to use for XML validation that you've already added to your integration account. If you're working with Health Insurance Portability and Accountability Act (HIPAA) schemas, see [HIPAA schemas](#hipaa-schemas).
2828

29-
* Before you can use the X12 connector, you must create an X12 [agreement](../logic-apps/logic-apps-enterprise-integration-agreements.md) between your trading partners and store that agreement in your integration account.
29+
* Before you can use the X12 connector, you must create an X12 [agreement](../logic-apps/logic-apps-enterprise-integration-agreements.md) between your trading partners and store that agreement in your integration account. If you're working with Health Insurance Portability and Accountability Act (HIPAA) schemas, you need to add a `schemaReferences` section to your agreement. For more information, see [HIPAA schemas](#hipaa-schemas).
3030

3131
<a name="receive-settings"></a>
3232

@@ -304,78 +304,74 @@ The **Default** row shows the validation rules that are used for an EDI message
304304

305305
<a name="hipaa-schemas"></a>
306306

307-
## HIPAA message types 277 and 837
307+
## HIPAA schemas and message types
308308

309-
When you work with HIPAA schemas and the 277 and 837 message types, you might have to take a few extra steps, based on the [schema document version number (GS8)](#outbound-control-version-number) that you want to use. Otherwise, you get this error message:
309+
When you work with HIPAA schemas and the 277 or 837 message types, you need to perform a few extra steps. The [document version numbers (GS8)](#outbound-control-version-number) for these message types have more than 9 characters, for example, "005010X222A1". Also, some document version numbers map to variant message types. If you don't reference the correct message type in your schema and in your agreement, you get this error message:
310310

311311
`"The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement."`
312312

313-
| Message type | Description |
314-
|--------------|-------------|
315-
| 277 | Health Care Information Status Notification |
316-
| 837 | Health Care Claim |
317-
| 837_D | Health Care Claim Dental |
318-
| 837_I | Health Care Claim Institutional |
319-
| 837_P | Health Care Claim Professional |
313+
This table lists the schema document version numbers, their message types, and any variants:
314+
315+
| Message type or variant | GS8 document version number | Description |
316+
|-------------------------|-----------------------------|-------------|
317+
| 277 | 005010X212 | Health Care Information Status Notification |
318+
| 837_I | 004010X096A1 <br>005010X223A1 <br>005010X223A2 | Health Care Claim Dental |
319+
| 837_D | 004010X097A1 <br>005010X224A1 <br>005010X224A2 | Health Care Claim Institutional |
320+
| 837_P | 004010X098A1 <br>005010X222 <br>005010X222A1 | Health Care Claim Professional |
320321
|||
321322

322-
If the schema document version number (GS8) that you want to use has more than 9 characters, for example, "005010X222A1", your schema needs to specify the message type that matches this special schema document version number. For more information, see [Example - Specify special schemas](#example-special-schema-version-number).
323+
You also need to disable EDI validation for these variant messages types because the version numbers result in an error that the character length is invalid.
323324

324-
> [!NOTE]
325-
> If you have to edit your existing schema, save the schema under a different name,
326-
> upload the edited schema to your integration account, and select the schema in your message settings.
327-
328-
| Message type | Schema document version number (GS8) |
329-
|--------------|--------------------------------------|
330-
| 277 | 005010X212 |
331-
| 277_A | 005010X214 |
332-
| 837_I | 004010X096A1 |
333-
| 837_I | 005010X223A1 |
334-
| 837_I | 005010X223A2 |
335-
| 837_D | 004010X097A1 |
336-
| 837_D | 005010X224A1 |
337-
| 837_D | 005010X224A2 |
338-
| 837_P | 004010X098A1 |
339-
| 837_P | 005010X222 |
340-
| 837_P | 005010X222A1 |
341-
|||
325+
Here are the steps to follow:
326+
327+
1. In your HIPAA schema, replace the current message type with the variant message type that matches the document version number.
328+
329+
For example, if your document version number is `005010X222A1`, replace `"X12_00501_837"` with `"X12_00501_837_P"`.
330+
331+
To update your schema, follow these steps:
332+
333+
1. In the Azure portal, go to your integration account, find the schema, [download, edit, rename, and upload your revised schema](../logic-apps/logic-apps-enterprise-integration-schemas.md#edit-schemas).
334+
335+
1. In your your agreement's message settings, select the revised schema.
336+
337+
1. In your agreement's `schemaReferences` object, add another item that has the variant message type that matches your document version number.
338+
339+
For example, suppose you want to use document version number `005010X222A1`. Your agreement has a `schemaReferences` section with these properties and values:
340+
341+
```json
342+
"schemaReferences": [
343+
{
344+
"messageId": "837",
345+
"schemaVersion": "00501",
346+
"schemaName": "X12_00501_837"
347+
}
348+
]
349+
```
350+
351+
In this `schemaReferences` section, add another item that has these values:
352+
353+
* `"messageId": "837_P"`
354+
* `"schemaVersion": "00501"`
355+
* `"schemaName": "X12_00501_837_P"`
356+
357+
```json
358+
"schemaReferences": [
359+
{
360+
"messageId": "837",
361+
"schemaVersion": "00501",
362+
"schemaName": "X12_00501_837"
363+
},
364+
{
365+
"messageId": "837_P",
366+
"schemaVersion": "00501",
367+
"schemaName": "X12_00501_837_P"
368+
}
369+
]
370+
```
371+
372+
1. Disable EDI validation for this message type by clearing the **EDI Validation** checkbox for each message type or for the **Default** message type, if you're using the default values for all message types.
342373

343-
You also have to disable EDI validation because having a document version number that's more than 9 characters is not valid and results in an error that the number length is invalid. You can disable validation for each message type or disable validation for all the message types by using the **Default** values.
344-
345-
![Validation properties](./media/logic-apps-enterprise-integration-x12/x12-send-settings-validation.png)
346-
347-
<a name="example-special-schema-version-number"></a>
348-
349-
### Example - Specify special schemas
350-
351-
Suppose you want to use "005010X222A1" as the schema document version number for the 837 message type, and your schema has a `schemaReferences` section with these properties and values:
352-
353-
```json
354-
"schemaReferences": [
355-
{
356-
"messageId": "837",
357-
"schemaVersion": "00501",
358-
"schemaName": "X12_00501_837"
359-
}
360-
]
361-
```
362-
363-
To use "005010X222A1" as the schema document version number, your schema needs to specify "837_P" as the message type by including another element in the `schemaReferences` section:
364-
365-
```json
366-
"schemaReferences": [
367-
{
368-
"messageId": "837",
369-
"schemaVersion": "00501",
370-
"schemaName": "X12_00501_837"
371-
},
372-
{
373-
"messageId": "837_P",
374-
"schemaVersion": "00501",
375-
"schemaName": "X12_00501_837_P"
376-
}
377-
]
378-
```
374+
![Validation properties](./media/logic-apps-enterprise-integration-x12/x12-disable-validation.png)
379375

380376
## Connector reference
381377

‎articles/logic-apps/media/logic-apps-enterprise-integration-x12/x12-disable-validation.png

6.84 KB
Loading

0 commit comments

Comments
 (0)