Conversation
0b8bbd6 to
3bc576a
Compare
3bc576a to
d548ba8
Compare
d548ba8 to
12dfe32
Compare
0f330d8 to
8df284c
Compare
8df284c to
0bafbc8
Compare
|
|
||
| A ViewDefinition that contains any de-identification extension can only be materialized as a `table`. Attempting to materialize as `view` or `materialized-view` returns HTTP 422 with an OperationOutcome: | ||
|
|
||
| > ViewDefinitions with de-identification extensions can only be materialized as 'table'. Views and materialized views expose cryptographic keys in PostgreSQL system catalogs. |
There was a problem hiding this comment.
I think we can remove this line because the next sentence already explains the restriction
|
|
||
| ## Pre-built ViewDefinitions | ||
|
|
||
| The IG package `io.health-samurai.de-identification.r4` provides ready-made Safe Harbor ViewDefinitions for common FHIR R4 resource types. Install it via FAR (Aidbox's artifact registry): |
|
|
||
| ## Pre-built ViewDefinitions | ||
|
|
||
| The IG package `io.health-samurai.de-identification.r4` provides ready-made Safe Harbor ViewDefinitions for common FHIR R4 resource types. Install it via FAR (Aidbox's artifact registry): |
There was a problem hiding this comment.
FAR is not used widely in docs, and in UI, it is not FAR anymore.
"via FAR (Aidbox's artifact registry)" -> "via [Artefact Registry](relative-path/artifact-registry/artifact-registry-overview) ("FHIR packages" in Aidbox UI)"
| ``` | ||
|
|
||
| This example uses the built-in PostgreSQL `left` function to keep only the first 4 characters (e.g. extracting just the year from a date string). | ||
|
|
There was a problem hiding this comment.
add here "See also: [Writing custom PostgreSQL functions](#writing-custom-postgresql-functions)"
|
|
||
| Restrict access to ViewDefinition resources using [AccessPolicy](../../access-control/authorization/README.md) to ensure only authorized users can view or modify de-identification configurations. | ||
|
|
||
| ### SQL injection prevention |
There was a problem hiding this comment.
We didn't write about SQL injection prevention in the docs before. It is cool that we do it, but we don't have to point to it. Maybe it's just me, but I think it is redundant here.
| } | ||
| ``` | ||
|
|
||
| ## Security considerations |
There was a problem hiding this comment.
Not much here. We can split "key management" and "encryption limitations" content into hints in "## encrypt" section.

No description provided.