@oystehr/sdk 3.0.0 → 3.0.1

package/src/resources/types/ZambdaFunction.ts

@@ -15,11 +15,11 @@ export interface ZambdaFunction {
   /**
    * The Zambda Function status provides information about the Functions state including whether it is ready to be invoked.
    */
-  status: string;
+  status: 'Draft' | 'Pending' | 'Active' | 'Failed' | 'Inactive' | 'Validating';
   /**
    * The trigger method for the Zambda Function determines how the Function is invoked. Learn more about the different types here, https://docs.oystehr.com/services/zambda/#types-of-zambdas.
    */
-  triggerMethod: string;
+  triggerMethod: 'http_auth' | 'http_open' | 'subscription' | 'cron';
   schedule?: ZambdaSchedule;
   /**
    * Info about the zip file that was uploaded for the Zambda Function.

package/src/resources/types/ZambdaUpdateParams.ts

@@ -10,11 +10,11 @@ export interface ZambdaUpdateParams {
   /**
    * The trigger method for the Zambda Function determines how the Function is invoked. Learn more about the different types here, https://docs.oystehr.com/services/zambda/#types-of-zambdas.
    */
-  triggerMethod?: string;
+  triggerMethod?: 'http_auth' | 'http_open' | 'subscription' | 'cron';
   schedule?: ZambdaSchedule;
   /**
    * The runtime to use for the Zambda Function. This property is optional and defaults to "nodejs20.x".
    */
-  runtime?: string;
+  runtime?: 'nodejs18.x' | 'nodejs20.x';
   id: string;
 }

package/src/resources/types/fhir.ts

@@ -15,12 +15,66 @@ import type {
 } from 'fhir/r5';
 
 export type FhirResource = FhirResourceR4B | FhirResourceR5;
-export type FhirBundle<F extends FhirResource> = F extends FhirResourceR4B ? BundleR4B<F> : BundleR5<F>;
-export type Bundle<F extends FhirResource> = FhirBundle<F> & { unbundle: (this: Bundle<F>) => F[] };
+// We're doing this "Omit dance" with the Bundle types because TypeScript
+// produces incorrect BundleEntry<F> types when F is a union of multiple FHIR
+// types. The guess is it's something about the conditional generic typing, but
+// we haven't found a different way to resolve it.
+//
+// No "omit dance":
+// entry: BundleEntry<Patient>[] | BundleEntry<Practitioner>[] | undefined
+// With "omit dance":
+// entry: (BundleEntry<Patient> | BundleEntry<Practitioner>)[] | undefined
+//
+// The latter can be used with array functions like `.find()`.
+export type FhirBundle<F extends FhirResource> = F extends FhirResourceR4B
+  ? Omit<BundleR4B<F>, 'entry'>
+  : Omit<BundleR5<F>, 'entry'>;
+export type Bundle<F extends FhirResource> = FhirBundle<F> & {
+  entry?: Array<BundleEntry<F>> | undefined;
+  unbundle: (this: Bundle<F>) => F[];
+};
 export type BundleEntry<F extends FhirResource> = F extends FhirResourceR4B ? BundleEntryR4B<F> : BundleEntryR5<F>;
 export type Binary<F extends FhirResource> = F extends FhirResourceR4B ? BinaryR4B : BinaryR5;
 export type OperationOutcome = OperationOutcomeR4B | OperationOutcomeR5;
 
+export type SearchParam = { name: string; value: string | number };
+
+export interface FhirSearchParams {
+  resourceType: string;
+  params?: SearchParam[];
+}
+
+export interface FhirGetParams {
+  resourceType: string;
+  id: string;
+}
+
+export type FhirCreateParams<T extends FhirResource> = T;
+
+export type FhirUpdateParams<T extends FhirResource> = T;
+
+export interface FhirPatchParams {
+  resourceType: string;
+  id: string;
+  operations: Operation[];
+}
+
+export interface FhirDeleteParams {
+  resourceType: string;
+  id: string;
+}
+
+export interface FhirHistorySearchParams {
+  resourceType: string;
+  id: string;
+}
+
+export interface FhirHistoryGetParams {
+  resourceType: string;
+  id: string;
+  versionId: string;
+}
+
 interface BatchInputBaseRequest {
   url: string;
 }