@greensecurity/javascript-sdk 0.45.0-beta.0 → 0.45.0-beta.2

package/src/models/components/fhirconfigcreate.ts

@@ -47,6 +47,22 @@ export type FhirConfigCreate = {
    */
   entities: FhirExtraEntities;
   projection?: string | undefined;
+  /**
+   * A JMESPath that decides whether a patient should be hidden (VIP, confidential, anonymized). When set it replaces the built-in checks, so a facility can describe its own rule instead of relying on the defaults. Some sites carry the anonymized marker on the encounter rather than the patient extension, which the built-ins do not look at.
+   *
+   * @remarks
+   *
+   * See [JMESPath](https://jmespath.org/)
+   */
+  restrictionFilter?: string | null | undefined;
+  /**
+   * A JMESPath that maps `{ patient, flags, encounter }` to the standard `{ isAnonymized, hasVipFlag }` shape. Takes precedence over restriction_filter, and covers the HL7 path as well as FHIR. Leave empty to fall back to restriction_filter or the built-in checks.
+   *
+   * @remarks
+   *
+   * See [JMESPath](https://jmespath.org/)
+   */
+  restrictionProjection?: string | null | undefined;
 };
 
 /** @internal */
@@ -173,6 +189,8 @@ export type FhirConfigCreate$Outbound = {
   notes?: string | undefined;
   entities: FhirExtraEntities$Outbound;
   projection?: string | undefined;
+  restriction_filter?: string | null | undefined;
+  restriction_projection?: string | null | undefined;
 };
 
 /** @internal */
@@ -192,12 +210,16 @@ export const FhirConfigCreate$outboundSchema: z.ZodType<
   notes: z.string().optional(),
   entities: FhirExtraEntities$outboundSchema,
   projection: z.string().optional(),
+  restrictionFilter: z.nullable(z.string()).optional(),
+  restrictionProjection: z.nullable(z.string()).optional(),
 }).transform((v) => {
   return remap$(v, {
     productionProfile: "production_profile",
     nonProductionProfile: "non_production_profile",
     appliesTo: "applies_to",
     activeProfile: "active_profile",
+    restrictionFilter: "restriction_filter",
+    restrictionProjection: "restriction_projection",
   });
 });
 

package/src/models/components/fhirextraentities.ts

@@ -3,6 +3,7 @@
  */
 
 import * as z from "zod/v3";
+import { remap as remap$ } from "../../lib/primitives.js";
 import { safeParse } from "../../lib/schemas.js";
 import { Result as SafeParseResult } from "../../types/fp.js";
 import * as types from "../../types/primitives.js";
@@ -14,6 +15,14 @@ import { SDKValidationError } from "../errors/sdkvalidationerror.js";
 export type FhirExtraEntities = {
   flags?: boolean | undefined;
   consents?: boolean | undefined;
+  /**
+   * Which Flag category a patient lookup should scope its search to. Epic refuses a Flag search that names no category, so a facility on Epic should set this or the search comes back rejected and the patient looks like they have no flags. Cerner and other servers allow a broad search and can leave it empty.
+   *
+   * @remarks
+   *
+   * Leave empty to let the client decide.
+   */
+  flagCategory?: string | null | undefined;
 };
 
 /** @internal */
@@ -24,11 +33,17 @@ export const FhirExtraEntities$inboundSchema: z.ZodType<
 > = z.object({
   flags: types.optional(types.boolean()),
   consents: types.optional(types.boolean()),
+  flag_category: z.nullable(types.string()).optional(),
+}).transform((v) => {
+  return remap$(v, {
+    "flag_category": "flagCategory",
+  });
 });
 /** @internal */
 export type FhirExtraEntities$Outbound = {
   flags?: boolean | undefined;
   consents?: boolean | undefined;
+  flag_category?: string | null | undefined;
 };
 
 /** @internal */
@@ -39,6 +54,11 @@ export const FhirExtraEntities$outboundSchema: z.ZodType<
 > = z.object({
   flags: z.boolean().optional(),
   consents: z.boolean().optional(),
+  flagCategory: z.nullable(z.string()).optional(),
+}).transform((v) => {
+  return remap$(v, {
+    flagCategory: "flag_category",
+  });
 });
 
 export function fhirExtraEntitiesToJSON(