You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| 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 |
321
321
|||
322
322
323
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.
324
324
325
-
Here are the steps to follow:
325
+
To specify these document version numbers and message types, follow these steps:
326
326
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.
328
328
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.
330
330
331
331
To update your schema, follow these steps:
332
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).
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).
334
334
335
335
1. In your your agreement's message settings, select the revised schema.
336
336
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.
338
338
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:
340
340
341
341
```json
342
342
"schemaReferences": [
@@ -348,12 +348,14 @@ Here are the steps to follow:
348
348
]
349
349
```
350
350
351
-
In this `schemaReferences` section, add another item that has these values:
351
+
In this `schemaReferences` section, add another entry that has these values:
352
352
353
353
*`"messageId": "837_P"`
354
354
*`"schemaVersion": "00501"`
355
355
*`"schemaName": "X12_00501_837_P"`
356
356
357
+
When you're done, your `schemaReferences` section looks like this:
358
+
357
359
```json
358
360
"schemaReferences": [
359
361
{
@@ -369,9 +371,9 @@ Here are the steps to follow:
369
371
]
370
372
```
371
373
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.
0 commit comments