Skip to content

Commit 8b01baa

Browse files
authored
Merge pull request AdobeDocs#217 from AdobeDocs/revert-215-jh_hipaa
Revert "HIPAA compliance"
2 parents 0d1a7e1 + c089d1b commit 8b01baa

File tree

2 files changed

+0
-30
lines changed

2 files changed

+0
-30
lines changed

src/pages/gateway/release-notes.md

-8
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,6 @@ keywords:
1414

1515
The following sections indicate when updates were made to API Mesh for Adobe Developer App Builder. Refer to the [Upgrade version](upgrade.md) for more information on upgrading versions.
1616

17-
## Jun 20, 2024
18-
19-
This release contains the following changes to API Mesh:
20-
21-
### Enhancements
22-
23-
API Mesh now supports HIPAA compliance. To create a mesh that contains Protected Health Information (PHI), refer to [HIPAA Compliance](./work-with-mesh.md#hipaa-compliance).
24-
2517
## May 21, 2024
2618

2719
This release contains the following changes to API Mesh:

src/pages/gateway/work-with-mesh.md

-22
Original file line numberDiff line numberDiff line change
@@ -216,25 +216,3 @@ Due to the limitations of API Mesh, responses contain both the newly created ali
216216
When you query a mesh using chained mutations, the mesh makes a separate call to the source for each mutation. This happens because GraphQL requests execute when the GraphQL server receives them, instead of proxying the calls. Because API Mesh supports multiple sources, it evaluates batched mutations and separates the information based on the source it is associated with.
217217

218218
These mutations are executed sequentially, calling one source after the other. When you call a source directly, it will only need one API call, but it will execute the batch mutations sequentially by calling their respective resolvers. These calls are more overt in API Mesh, because they are made by a network call, instead of an internal call. This means you will see multiple calls for chained mutations.
219-
220-
## HIPAA compliance
221-
222-
If your mesh's sources contain Protected Health Information (PHI), add `"HIPAA": true` to your mesh configuration file. This flag ensures that your mesh is compliant with the Health Insurance Portability and Accountability Act (HIPAA).
223-
224-
```json
225-
{
226-
"meshConfig": {
227-
"HIPAA": true,
228-
"sources": [
229-
{
230-
"name": "Healthcare store",
231-
"handler": {
232-
"graphql": {
233-
"endpoint": "<store_endpoint>"
234-
}
235-
}
236-
}
237-
]
238-
}
239-
}
240-
```

0 commit comments

Comments
 (0)