Skip to content

Commit 5326c17

Browse files
committed
Clarity edits
1 parent 35e9b53 commit 5326c17

File tree

2 files changed

+17
-15
lines changed

2 files changed

+17
-15
lines changed

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

Lines changed: 17 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -312,31 +312,31 @@ When you work with HIPAA schemas and the 277 or 837 message types, you need to p
312312

313313
This table lists the schema document version numbers, their message types, and any variants:
314314

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 |
315+
| Message type or variant | Description | GS8 document version number |
316+
|-------------------------|--------------|-----------------------------|
317+
| 277 | Health Care Information Status Notification | 005010X212 |
318+
| 837_I | Health Care Claim Dental | 004010X096A1 <br>005010X223A1 <br>005010X223A2 |
319+
| 837_D | Health Care Claim Institutional | 004010X097A1 <br>005010X224A1 <br>005010X224A2 |
320+
| 837_P | Health Care Claim Professional | 004010X098A1 <br>005010X222 <br>005010X222A1 |
321321
|||
322322

323323
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.
324324

325-
Here are the steps to follow:
325+
To specify these document version numbers and message types, follow these steps:
326326

327-
1. In your HIPAA schema, replace the current message type with the variant message type that matches the document version number.
327+
1. In your HIPAA schema, replace the current message type with the variant message type for the document version number that you want to use.
328328

329-
For example, if your document version number is `005010X222A1`, replace `"X12_00501_837"` with `"X12_00501_837_P"`.
329+
For example, suppose you want to use document version number `005010X222A1` with the `837` message type. In your schema, replace each `"X12_00501_837"` value with the `"X12_00501_837_P"` value instead.
330330

331331
To update your schema, follow these steps:
332332

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).
333+
1. In the Azure portal, go to your integration account. Find and download your schema. Replace the message type and rename the schema file, and upload your revised schema to your integration account. For more information, see [Edit schemas](../logic-apps/logic-apps-enterprise-integration-schemas.md#edit-schemas).
334334

335335
1. In your your agreement's message settings, select the revised schema.
336336

337-
1. In your agreement's `schemaReferences` object, add another item that has the variant message type that matches your document version number.
337+
1. In your agreement's `schemaReferences` object, add another entry that specifies the variant message type that matches your document version number.
338338

339-
For example, suppose you want to use document version number `005010X222A1`. Your agreement has a `schemaReferences` section with these properties and values:
339+
For example, suppose you want to use document version number `005010X222A1` for the `837` message type. Your agreement has a `schemaReferences` section with these properties and values:
340340

341341
```json
342342
"schemaReferences": [
@@ -348,12 +348,14 @@ Here are the steps to follow:
348348
]
349349
```
350350

351-
In this `schemaReferences` section, add another item that has these values:
351+
In this `schemaReferences` section, add another entry that has these values:
352352

353353
* `"messageId": "837_P"`
354354
* `"schemaVersion": "00501"`
355355
* `"schemaName": "X12_00501_837_P"`
356356

357+
When you're done, your `schemaReferences` section looks like this:
358+
357359
```json
358360
"schemaReferences": [
359361
{
@@ -369,9 +371,9 @@ Here are the steps to follow:
369371
]
370372
```
371373

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.
374+
1. In your agreement's message settings, disable EDI validation for this message type by clearing the **EDI Validation** checkbox either for each message type or for all message types if you're using the **Default** values.
373375

374-
![Validation properties](./media/logic-apps-enterprise-integration-x12/x12-disable-validation.png)
376+
![Disable validation for all message types or each message type](./media/logic-apps-enterprise-integration-x12/x12-disable-validation.png)
375377

376378
## Connector reference
377379

13 Bytes
Loading

0 commit comments

Comments
 (0)