@awell-health/awell-extensions 1.1.0-beta10 → 1.1.1

package/dist/extensions/healthie/actions/index.d.ts

@@ -49,7 +49,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, "appointmentId", never>;
+    }, "appointmentId">;
     createTask: import("@awell-health/extensions-core").Action<{
         patientId: {
             id: string;
@@ -123,7 +123,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, "taskId", never>;
+    }, "taskId">;
     getAppointment: import("@awell-health/extensions-core").Action<{
         appointmentId: {
             id: string;
@@ -146,7 +146,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, "date" | "patientId" | "appointmentTypeId" | "appointmentTypeName" | "appointmentStatus" | "contactType", never>;
+    }, "date" | "patientId" | "appointmentTypeId" | "appointmentTypeName" | "appointmentStatus" | "contactType">;
     getPatient: import("@awell-health/extensions-core").Action<{
         patientId: {
             id: string;
@@ -169,7 +169,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, "email" | "firstName" | "lastName" | "gender" | "dob" | "isoSex" | "phoneNumber" | "primaryProviderId" | "groupName", never>;
+    }, "email" | "firstName" | "lastName" | "gender" | "dob" | "isoSex" | "phoneNumber" | "primaryProviderId" | "groupName">;
     sendChatMessage: import("@awell-health/extensions-core").Action<{
         healthie_patient_id: {
             id: string;
@@ -207,7 +207,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, "conversationId", never>;
+    }, "conversationId">;
     createPatient: import("@awell-health/extensions-core").Action<{
         first_name: {
             id: string;
@@ -276,7 +276,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, "healthiePatientId", never>;
+    }, "healthiePatientId">;
     updatePatient: import("@awell-health/extensions-core").Action<{
         id: {
             id: string;
@@ -384,7 +384,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     applyTagToPatient: import("@awell-health/extensions-core").Action<{
         id: {
             id: string;
@@ -415,7 +415,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     removeTagFromPatient: import("@awell-health/extensions-core").Action<{
         id: {
             id: string;
@@ -446,7 +446,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     createChartingNote: import("@awell-health/extensions-core").Action<{
         healthie_patient_id: {
             id: string;
@@ -498,7 +498,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     sendFormCompletionRequest: import("@awell-health/extensions-core").Action<{
         healthie_patient_id: {
             id: string;
@@ -585,7 +585,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     archivePatient: import("@awell-health/extensions-core").Action<{
         id: {
             id: string;
@@ -609,7 +609,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     /**
      * There is bug in Healthie that prevents linking an address with a patient
      * Waiting for fix
@@ -644,7 +644,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     deleteAppointment: import("@awell-health/extensions-core").Action<{
         id: {
             id: string;
@@ -668,7 +668,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     cancelAppointment: import("@awell-health/extensions-core").Action<{
         id: {
             id: string;
@@ -692,7 +692,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     /**
      *  Specs of this API endpoint are unclear so we are not sure what
      *  functional value it delivers in the current state. Needs to be revisited.
@@ -720,7 +720,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     completeTask: import("@awell-health/extensions-core").Action<{
         id: {
             id: string;
@@ -744,7 +744,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     assignPatientToGroup: import("@awell-health/extensions-core").Action<{
         id: {
             id: string;
@@ -775,7 +775,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     getMetricEntry: import("@awell-health/extensions-core").Action<{
         patientId: {
             id: string;
@@ -806,7 +806,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, "metricId" | "metricValue" | "createdAt", never>;
+    }, "metricId" | "metricValue" | "createdAt">;
     updatePatientQuickNote: import("@awell-health/extensions-core").Action<{
         patientId: {
             id: string;
@@ -842,7 +842,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     createMetricEntry: import("@awell-health/extensions-core").Action<{
         userId: {
             id: string;
@@ -880,7 +880,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, string, never>;
+    }, string>;
     checkPatientTag: import("@awell-health/extensions-core").Action<{
         id: {
             id: string;
@@ -909,7 +909,7 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, "hasTag", never>;
+    }, "hasTag">;
     checkScheduledAppointments: import("@awell-health/extensions-core").Action<{
         patientId: {
             id: string;
@@ -939,5 +939,5 @@ export declare const actions: {
             required: true;
             description: string;
         };
-    }, "isScheduled", never>;
+    }, "isScheduled">;
 };

package/dist/extensions/icd/actions/index.d.ts

@@ -6,6 +6,6 @@ declare const _default: {
             description: string;
             type: import("@awell-health/extensions-core").FieldType.STRING;
         };
-    }, {}, "codes" | "stringResponse", never>;
+    }, {}, "codes" | "stringResponse">;
 };
 export default _default;

package/dist/extensions/index.js

@@ -24,7 +24,6 @@ var __importStar = (this && this.__importStar) || function (mod) {
 };
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.extensions = exports.markdown = void 0;
-// import { AvaAi } from './avaAi'
 const awell_1 = require("./awell");
 const calDotCom_1 = require("./calDotCom");
 const calendly_1 = require("./calendly");
@@ -42,7 +41,6 @@ const math_1 = require("./math");
 const messagebird_1 = require("./messagebird");
 const metriport_1 = require("./metriport");
 const twilio_1 = require("./twilio");
-// import { Wellinks } from './wellinks-public'
 const sendgrid_extension_1 = require("./sendgrid-extension");
 const cmDotCom_1 = require("./cmDotCom");
 const talkDesk_1 = require("./talkDesk");
@@ -59,13 +57,12 @@ const athenahealth_1 = require("./athenahealth");
 const icd_1 = require("./icd");
 const textline_1 = require("./textline");
 const medplum_1 = require("./medplum");
+const dockHealth_1 = require("./dockHealth");
+const stripe_1 = require("./stripe");
 const json = __importStar(require("./markdown.json"));
 const external_server_1 = require("./external-server");
 exports.markdown = json;
 exports.extensions = [
-    // AvaAi, Best to disable this until we cleared out data privacy & HIPAA with OpenAI
-    // ZusHealth is not ready for public use yet
-    // ZusHealth,
     awell_1.Awell,
     athenahealth_1.athenahealth,
     calDotCom_1.CalDotCom,
@@ -74,6 +71,7 @@ exports.extensions = [
     cloudinary_1.Cloudinary,
     cmDotCom_1.CmDotCom,
     collectData_1.CollectData,
+    dockHealth_1.dockHealth,
     docuSign_1.DocuSign,
     dropboxSign_1.DropboxSign,
     elation_1.Elation,
@@ -89,18 +87,17 @@ exports.extensions = [
     mailgun_1.Mailgun,
     math_1.MathExtension,
     messagebird_1.MessageBird,
+    medplum_1.Medplum,
     metriport_1.Metriport,
     nexuzhealth_1.nexuzhealth,
     sendbird_1.Sendbird,
     sendgrid_extension_1.Sendgrid,
-    cmDotCom_1.CmDotCom,
+    stripe_1.stripe,
     talkDesk_1.TalkDesk,
+    textline_1.TextLine,
     transform_1.Transform,
     twilio_1.Twilio,
-    // Wellinks,
     zendesk_1.Zendesk,
     westFax_1.WestFax,
-    textline_1.TextLine,
-    medplum_1.Medplum,
 ];
 //# sourceMappingURL=index.js.map

package/dist/extensions/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../extensions/index.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,kCAAkC;AAClC,mCAA+B;AAC/B,2CAAuC;AACvC,yCAAqC;AACrC,mDAA+C;AAC/C,6CAAyC;AACzC,+CAA2C;AAC3C,uCAAmC;AACnC,iDAA6C;AAC7C,yCAAqC;AACrC,yCAAqC;AACrC,+CAA0C;AAC1C,2CAAuC;AACvC,uCAAmC;AACnC,iCAAsC;AACtC,+CAA2C;AAC3C,2CAAuC;AACvC,qCAAiC;AACjC,+CAA+C;AAC/C,6DAA+C;AAC/C,yCAAqC;AACrC,yCAAqC;AACrC,yCAAqC;AACrC,yCAAqC;AACrC,2CAAuC;AACvC,yCAAqC;AACrC,uCAAmC;AACnC,uCAAmC;AACnC,uCAAmC;AACnC,+CAA2C;AAC3C,+CAA2C;AAC3C,iDAA6C;AAC7C,+BAA2B;AAC3B,yCAAqC;AACrC,uCAAmC;AAEnC,sDAAuC;AACvC,uDAAkD;AAGrC,QAAA,QAAQ,GAAa,IAAI,CAAA;AAEzB,QAAA,UAAU,GAAG;IACxB,oFAAoF;IACpF,4CAA4C;IAC5C,aAAa;IACb,aAAK;IACL,2BAAY;IACZ,qBAAS;IACT,mBAAQ;IACR,6BAAa;IACb,uBAAU;IACV,mBAAQ;IACR,yBAAW;IACX,mBAAQ;IACR,yBAAW;IACX,iBAAO;IACP,2BAAY;IACZ,gCAAc;IACd,mBAAQ;IACR,mBAAQ;IACR,wBAAU;IACV,SAAG;IACH,iBAAO;IACP,mBAAQ;IACR,qBAAS;IACT,iBAAO;IACP,oBAAa;IACb,yBAAW;IACX,qBAAS;IACT,yBAAW;IACX,mBAAQ;IACR,6BAAQ;IACR,mBAAQ;IACR,mBAAQ;IACR,qBAAS;IACT,eAAM;IACN,YAAY;IACZ,iBAAO;IACP,iBAAO;IACP,mBAAQ;IACR,iBAAO;CACR,CAAA"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../extensions/index.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,mCAA+B;AAC/B,2CAAuC;AACvC,yCAAqC;AACrC,mDAA+C;AAC/C,6CAAyC;AACzC,+CAA2C;AAC3C,uCAAmC;AACnC,iDAA6C;AAC7C,yCAAqC;AACrC,yCAAqC;AACrC,+CAA0C;AAC1C,2CAAuC;AACvC,uCAAmC;AACnC,iCAAsC;AACtC,+CAA2C;AAC3C,2CAAuC;AACvC,qCAAiC;AACjC,6DAA+C;AAC/C,yCAAqC;AACrC,yCAAqC;AACrC,yCAAqC;AACrC,yCAAqC;AACrC,2CAAuC;AACvC,yCAAqC;AACrC,uCAAmC;AACnC,uCAAmC;AACnC,uCAAmC;AACnC,+CAA2C;AAC3C,+CAA2C;AAC3C,iDAA6C;AAC7C,+BAA2B;AAC3B,yCAAqC;AACrC,uCAAmC;AACnC,6CAAyC;AACzC,qCAAiC;AAEjC,sDAAuC;AACvC,uDAAkD;AAGrC,QAAA,QAAQ,GAAa,IAAI,CAAA;AAEzB,QAAA,UAAU,GAAG;IACxB,aAAK;IACL,2BAAY;IACZ,qBAAS;IACT,mBAAQ;IACR,6BAAa;IACb,uBAAU;IACV,mBAAQ;IACR,yBAAW;IACX,uBAAU;IACV,mBAAQ;IACR,yBAAW;IACX,iBAAO;IACP,2BAAY;IACZ,gCAAc;IACd,mBAAQ;IACR,mBAAQ;IACR,wBAAU;IACV,SAAG;IACH,iBAAO;IACP,mBAAQ;IACR,qBAAS;IACT,iBAAO;IACP,oBAAa;IACb,yBAAW;IACX,iBAAO;IACP,qBAAS;IACT,yBAAW;IACX,mBAAQ;IACR,6BAAQ;IACR,eAAM;IACN,mBAAQ;IACR,mBAAQ;IACR,qBAAS;IACT,eAAM;IACN,iBAAO;IACP,iBAAO;CACR,CAAA"}

package/dist/extensions/markdown.json

@@ -3,13 +3,9 @@
     "readme": "---\ntitle: Athena\ndescription: Athena offers medical groups, hospitals, and health systems cloud-based EHR, practice management, and patient engagement services that seamlessly connect care and drive results for every client. \n---\n\n## Athenahealth\n\nAthena offers medical groups, hospitals, and health systems cloud-based EHR, practice management, and patient engagement services that seamlessly connect care and drive results for every client.\n\n## Extension settings\n\nFor the extension to function correctly, you must configure the following settings:\n\n- Auth server URL (e.g. https://api.preview.platform.athenahealth.com/oauth2/v1/token)\n- Client ID\n- Client secret\n- API URL (https://api.preview.platform.athenahealth.com)\n- Scope\n- Practice ID\n\n\n## Actions\n\n### Create patient\n\nCreates a patient in athenahealth. First name, last name, date of birth, email, and department ID are required. If a patient with the same name, date of birth, and email already exists, a new patient record will not be created. Instead, the existing patient's ID will be returned.\n\n### Get patient\n\nRetrieve the details of a given patient within a given practice.\n\n### Get appointment\n\nRetrieve the details of an appointment.\n\n### Create appointment note\n\nCreate a note which will be appended to an appointment",
     "changelog": "# Athena changelog"
   },
-  "avaAi": {
-    "readme": "---\ntitle: AvaAI\ndescription: Experimental extension to introduce AI actions in care flows.\n---\n# Awell Virtual (AI) Assistant - Ava\n\n## Extension settings\n\nIn order to set up this extension, you will need to provide an Open AI API key.\n\n## Custom Actions\n\n### Generate patient summary\n\nGenerates a human-readable summary about the patient based on the characteristics in the patient's profile.\n\nYou can specify which characteristics of the patient you would like to include by providing a comma-separated string with the below possible options:\n\n- first_name\n- last_name\n- street\n- city\n- country\n- state\n- zip\n- birth_date\n- email\n- mobile_phone\n- phone\n- national_registry_number\n- patient_code\n- preferred_language\n- sex\n\nIf no characteristics are passed, by default a summary will be generated that includes all characteristics.",
-    "changelog": "# Ava changelog"
-  },
   "awell": {
-    "readme": "---\ntitle: Awell Workflow\ndescription: Enrich your care flows with powerful Awell actions.\n---\n\n# Awell API extension\n\n## Extension settings\n\nYou will need to provide the [API URL](https://developers.awellhealth.com/awell-orchestration/api-reference/overview/endpoints) and an [API key](https://developers.awellhealth.com/awell-orchestration/api-reference/overview/authorization).\n\n## Custom Actions\n\n### Start care flow\n\nStarts a new care flow for the patient enrolled in your current care flow.\n\n**Passing baseline info:**\nPlease read the documentation on [our developer hub](https://developers.awellhealth.com/awell-orchestration/api-reference/mutations/start-pathway) to learn more about how to pass baseline info.\n\n**Example of how to configure a value for the baseline info action field:**\n\n```json\n[\n  {\n    \"data_point_definition_id\": \"age\",\n    \"value\": \"29\"\n  },\n  {\n    \"data_point_definition_id\": \"dob\",\n    \"value\": \"1993-11-30\"\n  }\n]\n```\n\n### Stop care flow\n\nStops the care flow the patient is currently enrolled in. A reason is why you are stopping the care flow is mandatory.\n\n### Update patient\n\nAllows updating patient data for the patient currently enrolled in the care flow.\n\n### Is patient already enrolled in care flow\n\nChecks whether the patient is already enrolled in a care flow definition. The care flow the patient is currently enrolled in does not count and is excluded from the results.\n\n**Action fields:**\n\n- pathwayStatus: a comma-separated string of care flow statuses that will be used when looking for care flows the patient is already enrolled in. By default, we only look at active care flows. Options: \"active\", \"completed\", \"missing_baseline_info\", \"starting\", and \"stopped\".\n- careFlowDefinitionIds: a comma-separated string of care flow definition ids that will be used when looking for care flows the patient is already enrolled in. By default, we only search for care flows that match the current care flow definition id (i.e. is the patient already included in the current care flow?).\n\n**Data points:**\n\n- result: a boolean indicating whether the patient is already enrolled in another care flow that matches your criteria (status & care flow definition id)\n- nbrOfResults: the number of care flows found for the patient that match the criteria.\n- careFlowIds: a comma-separated string of care flow ids that matched your search criteria. It will be empty when the result is `false` because then there are no other care flow ids that match your criteria.\n\n### Search patients by patient code\n\nSearch whether, apart from the patient currently enrolled in the care flow, another patient with the same `patient_code` already exists.\n\n**Data points:**\n\n1. patientAlreadyExists: a boolean which will be true if minimum one patient with the patient code already exists.\n2. numberOfPatientsFound: the number of patients found with the same patient code.\n3. awellPatientIds: a comma-separated string of all Awell patient ids (except the current patient) that have the same patient code as the patient currently enrolled in the care flow. Will return an empty string when there are no other patients with the same patient code.\n\n## Webhooks\n\nWebhooks in the Awell extension offer ways to trigger a care flow based on the end of another care flow, or from any event that happens in your system (via the pathwayStart webhook).\n",
-    "changelog": "# Awell changelog\n\n## October 26, 2023\n\nGeneric webhook to start a care flow added\n\n## April 19, 2023\n\nStop care flow action added.\nSearch patients by patient code action was added.\n\"Is patient enrolled in care flow\" action added.\n"
+    "readme": "---\ntitle: Awell Workflow\ndescription: Enrich your care flows with powerful Awell actions.\n---\n\n# Awell API extension\n\n## Extension settings\n\nYou will need to provide the [API URL](https://developers.awellhealth.com/awell-orchestration/api-reference/overview/endpoints) and an [API key](https://developers.awellhealth.com/awell-orchestration/api-reference/overview/authorization).\n\n## Custom Actions\n\n### Start care flow\n\nStarts a new care flow for the patient enrolled in your current care flow.\n\n**Passing baseline info:**\nPlease read the documentation on [our developer hub](https://developers.awellhealth.com/awell-orchestration/api-reference/mutations/start-pathway) to learn more about how to pass baseline info.\n\n**Example of how to configure a value for the baseline info action field:**\n\n```json\n[\n  {\n    \"data_point_definition_id\": \"age\",\n    \"value\": \"29\"\n  },\n  {\n    \"data_point_definition_id\": \"dob\",\n    \"value\": \"1993-11-30\"\n  }\n]\n```\n\n### Stop care flow\n\nStops the care flow the patient is currently enrolled in. A reason is why you are stopping the care flow is mandatory.\n\n### Update patient\n\nAllows updating patient data for the patient currently enrolled in the care flow.\n\n### Is patient already enrolled in care flow\n\nChecks whether the patient is already enrolled in a care flow definition. The care flow the patient is currently enrolled in does not count and is excluded from the results.\n\n**Action fields:**\n\n- pathwayStatus: a comma-separated string of care flow statuses that will be used when looking for care flows the patient is already enrolled in. By default, we only look at active care flows. Options: \"active\", \"completed\", \"missing_baseline_info\", \"starting\", and \"stopped\".\n- careFlowDefinitionIds: a comma-separated string of care flow definition ids that will be used when looking for care flows the patient is already enrolled in. By default, we only search for care flows that match the current care flow definition id (i.e. is the patient already included in the current care flow?).\n\n**Data points:**\n\n- result: a boolean indicating whether the patient is already enrolled in another care flow that matches your criteria (status & care flow definition id)\n- nbrOfResults: the number of care flows found for the patient that match the criteria.\n- careFlowIds: a comma-separated string of care flow ids that matched your search criteria. It will be empty when the result is `false` because then there are no other care flow ids that match your criteria.\n\n### Search patients by patient code\n\nNote that this action is deprecated and we recommend using [identifiers](https://developers.awellhealth.com/awell-orchestration/docs/misc/patient-identifiers) instead.\n\nSearch whether, apart from the patient currently enrolled in the care flow, another patient with the same `patient_code` already exists.\n\n**Data points:**\n\n1. patientAlreadyExists: a boolean which will be true if minimum one patient with the patient code already exists.\n2. numberOfPatientsFound: the number of patients found with the same patient code.\n3. awellPatientIds: a comma-separated string of all Awell patient ids (except the current patient) that have the same patient code as the patient currently enrolled in the care flow. Will return an empty string when there are no other patients with the same patient code.\n\n### Get patient by identifier\n\nThis action lets you check if a patient with a specific identifier already exists in Awell. It's particularly useful when a patient's identity is initially anonymous during the start of the care flow, but later becomes identifiable through the identifiers collected during the care flow. This check ensures whether a patient with that identifier is already present or not.\n\n### Add identifier to patient\n\nThis action enables adding an identifier to the current patient. We recommend using the \"Get patient by identifier\" action first to verify if a patient with that identifier already exists. If the identifier isn't already associated with another patient, it's safe to add it to the current patient. If a match is found, implementing a strategy for deduplication is advisable.\n\n## Webhooks\n\nWebhooks in the Awell extension offer ways to trigger a care flow based on the end of another care flow, or from any event that happens in your system (via the pathwayStart webhook).\n",
+    "changelog": "# Awell changelog\n\n## April 2024\n\nTwo new action were added: \"Get patient by identifier\" and \"Add identifier to patient\".\n\n## October 26, 2023\n\nGeneric webhook to start a care flow added\n\n## April 19, 2023\n\nStop care flow action added.\nSearch patients by patient code action was added.\n\"Is patient enrolled in care flow\" action added.\n"
   },
   "calDotCom": {
     "readme": "---\ntitle: Cal.com\ndescription: Cal.com is a modern and open source scheduling platform. With HIPAA, GDPR and SOC2 compliance, you can ensure that data is well-protected and that makes Cal.com a great fit for healthcare use cases.\n---\n\n# Cal.com\n\n[Cal.com](https://cal.com/) is a modern and **open source** scheduling platform. With HIPAA, GDPR and SOC2 compliance, you can ensure that data is well-protected and that makes Cal.com a great fit for healthcare use cases.\n\n## Cal.com x Awell\n\nThis extension allows you to let a stakeholder (eg: a patient) book an appointment as part of a care flow and to retrieve the booking details of an appointment.\n\n## Extension settings\n\nIn order to set up this extension, **you will need to provide a Cal.com API key**. You can obtain an API key via the Cal.com portal (`Settings > Developer > API keys`).\n\n## Custom Actions\n\n### Book appointment action\n\nYou can add this action to your care flow to enable a stakeholder (eg: a patient) to book an appointment in a predefined calendar. This is a **stakeholder-actionable action** which means it requires an actual user to book an appointment. Also note that this is a blocking action and that the care flow will not progress - unless there are parallel tracks or transitions - until the action/activity is completed (i.e. an appointment was booked).\n\n**The actual booking of the appointment can happen in two ways:**\n\n1. With Awell Hosted Pages: when the \"Book appointment\" action is activated, we serve the booking widget to the stakeholder so they can book an appointment directly from within Awell Hosted Pages.\n2. If you are not leveraging Awell Hosted Pages but have built a custom integration then we expose you all the details via our API so you can either create a Cal.com booking widget yourself or redirect the user to the Cal.com platform. Additionally, we expose a mutation that allows you to complete the activity and pass in the required data.\n\nBelow you can find an overview of all Awell Apps and whether they support rendering of the booking widget.\n\n| App                           | Supported |\n| ----------------------------- | --------- |\n| Awell Hosted Pages            | Yes       |\n| Your app (custom integration) | Yes       |\n| Awell Care                    | No        |\n| Awell MyCare                  | No        |\n\n#### Data points\n\nAdding this action to your care flow will expose a new data point you can use in your care flow, the `bookingId`. When the care flow is orchestrated and the book appointment activity is completed, the id of the actual booking will be ingested as the value of that `bookingId` data point.\n\n### Get booking action\n\nThis action allows you to fetch the details of a booking based on the provided `bookingId`. This action will make the following data points available for you to use in your care flow:\n\n1. Event type ID\n2. Title\n3. Description\n4. Start time\n5. End time\n6. Status\n7. Cancel URL\n8. Reschedule URL\n9. Video call URL (if available)\n10. First Attendee's name\n12. First Attendee's timezone\n12. First Attendee's email\n13. Organizer's email\n\n### Update booking\n\nUpdates a booking and saves new `bookingId` and `bookingUid` as Data Points. Values possible to update:\n\n- Title - Title of Booking event\n- Description - Description of the meeting\n- Status - Status of the meeting to be set. Possible values: \"ACCEPTED\", \"PENDING\", \"CANCELLED\", \"REJECTED\".\n- Start - Start time of the Event in ISO 8601 format, e.g. 2023-05-24T13:00:00.000Z. Please note that start/end time must be within user's availability hours.\n- End - End time of the Event in ISO 8601 format, e.g. 2023-05-24T13:00:00.000Z. Please note that start/end time must be within user's availability hours.\n\n### Create booking\n\nCreates a booking and saves new `bookingId` as Data Points. Available fields:\n\n- Event Type ID - ID of the event type to book\n- Responses - Object containing email, name, location\n  - ```json\n        \"responses\": {\n            \"name\": \"John Doe\",\n            \"email\": \"john.doe@example.com\",\n            \"location\": \"Calcom HQ\"\n        },\n    ```\n- Metadata - Any metadata associated with the booking\n- Timezone - Timezone of the Attendee\n- Language - Language of the Attendee\n- Recurring Event ID - Recurring Event ID if the event is recurring\n- Title - Title of Booking event\n- Description - Description of the meeting\n- Status - Status of the meeting to be set. Possible values: \"ACCEPTED\", \"PENDING\", \"CANCELLED\", \"REJECTED\".\n- Start - Start time of the Event in ISO 8601 format, e.g. 2023-05-24T13:00:00.000Z. Please note that start/end time must be within user's availability hours.\n- End - End time of the Event in ISO 8601 format, e.g. 2023-05-24T13:00:00.000Z. Please note that start/end time must be within user's availability hours.\n\n### Delete Boooking\n\nDeletes a Booking with a given ID.\n\n## Pricing\n\n**This extension is free** but keep in mind that you might need a paid plan for Cal.com depending on your needs.\n\n## Limitations\n\n### Rescheduling\n\nWhen a previously made booking is rescheduled, there is no way yet to get the new/updated booking details into the care flow or have the care flow react on the updated booking.\n\nAlso note that when a booking is rescheduled, Cal.com doesn't update the original booking resource but creates a new one instead. As far as we know, there is no reference from the old booking to the new (rescheduled) booking.\n\n#### Example\n\nAn appointment has been booked with Cal.com and we have the below booking resource:\n\n```json\n{\n    ...,\n    \"bookingId\": \"1\",\n    \"date\": \"Jan 1, 2023\"\n}\n```\n\nHowever, the patient reschedules the booking to Jan 10, 2023. When querying Cal.com's API (`GET v1/bookings/{bookingId}`), it will still return the old booking date instead of the new/rescheduled date.\n\n```json\n{\n    ...,\n    \"bookingId\": \"1\",\n    \"date\": \"Jan 1, 2023\"\n}\n```\n\n## Webhooks\n\nWebhooks offer a great way to automate the flow with Awell when invitees schedule, cancel, or reschedule events, or when the meeting ends.\n\n**Important notes:**\n\n1. An Awell webhook endpoint can only listen to one event type. So make sure that when you create a webhook in Cal.com, the subscriber URL and the event trigger match the Awell webhook endpoint. This also means there can only be one event type per subscriber URL.\n2. Using a secret to verify the authenticity of the received payload is not yet supported.\n3. Custom payload templates are not supported, please use the default ones.\n",
@@ -35,6 +31,10 @@
     "readme": "---\ntitle: Advanced data collection\ndescription: Collect data from your users using a variety of input types and data sources\n---\n\nThis extension allows you to collect data from your users using a variety of more advanced input types and data sources.\n\n## Extension settings\n\nIn order to set up this extension, no settings are required.\n\n## Custom Actions\n\n### Dynamic choice selector\n\nStandard select questions in Awell forms have a discrete set of choices to select from that are defined at the time that the form is created. If the list of choices to present to your responders isn't known at the time the form is being built, or changes often, this action allows you to load choices dynamically from a remote data source.\n\nDynamically-loaded choices must adhere to the following format in a list form (i.e. an array):\n\n```json\n{\n  \"id\": \"unique-id\",\n  \"label\": \"Choice label\",\n  \"value\": \"Choice value\"\n}\n```\n\nAdditionally, you can specify a free text search field (`Options - Search query param` field) to allow users to search through the choices. This is optional but highly recommended. If not specified, the choices will be fetched on question load and presented in a static list that cannot be filtered.\n\nAs an example, using the endpoint `https://example.com/choices` with a query parameter `search` (e.g. `https://example.com/choices?search=QUERY` where `QUERY` is whatever the user typed into the input), then the API is expected to return the choices based on that match the search term.\n\nWe recommend that your search logic returns an _alphabetically-sorted_ list of all options where the _lowercase_ label names _contain_ the _lowercase_ search term.\n\n```js\n// Example search logic\nconst searchTerm = req.query.search\nconst results = []\n\noptions.forEach((option) => {\n  if (option.label.toLowerCase().includes(searchTerm.toLowerCase())) {\n    results.push({\n      label: option.label,\n      value: option.value,\n      id: option.id,\n    })\n  }\n})\n\nconst sortedResults = results.sort((a, b) => a.label.localeCompare(b.label))\nres.json(results)\n```\n",
     "changelog": "# Collect Data changelog\n"
   },
+  "dockHealth": {
+    "readme": "---\ntitle: Dock Health\ndescription: HIPAA-compliant task management and workflow automation for healthcare. Assign, track, automate, and complete administrative to-do lists.\n---\n\n## Dock Health\n\nHIPAA-compliant task management and workflow automation for healthcare. Assign, track, automate, and complete administrative to-do lists.\n\n## Extension settings\n\nFor the extension to function correctly, you must configure the following settings. You can read more about these settings [here](https://github.com/DockHealth/dockhealth-api).\n\n- Environment (production or development)\n- Client ID\n- Client secret\n- API key\n- Organiation identifier\n- User identifier",
+    "changelog": "# Dock Health changelog"
+  },
   "docuSign": {
     "readme": "---\ntitle: DocuSign\ndescription: Make your business faster, simpler and more cost-efficient with electronic agreements. Agree with confidence, with intuitive signing experiences across virtually any device.\n---\n# DocuSign\n\nMake your business faster, simpler and more cost-efficient with electronic agreements. Agree with confidence, with intuitive signing experiences across virtually any device.\n\n## Extension settings\n\nIn order to set up this extension, you will need to provide the following settings:\n\n1. **Integration key (client ID)** - An integration key identifies your integration and links to its configuration values. This can be obtained in your developer account from the **Apps and Keys** page\n2. **API Account ID** - A GUID value that identifies your account. This can be obtained in your developer account from the **Apps and Keys** page\n3. **Impersonated User ID (UserID)** - This is a GUID identifying the DocuSign user that you will be impersonating with the access token. Your own User ID can be found at the top of the **Apps and Keys** page.\n4. **RSA private key (in Base64 format)** - This is for the integration key you obtained above and can also be created on the **Apps and Keys** page (DocuSign also allows uploading your own keys). You only need the private key, and it can only be copied once. Make sure to retain it for your records. Provide it in Base64 format - if you copy the key as is, it will not be valid as newlines and formatting won't be persisted.\n5. **Base API URL** - Base API URL for API calls matching your environment on DocuSign. Defaults to: https://demo.docusign.net. Can be obtained from **Account Base URI** section of the **Apps and Keys** page or the `base_uri` property in the response of a call to the `/oauth/userinfo`.\n   1. `DEV` environment: https://demo.docusign.net (default)\n   2. `PRODUCTION` environment: **https://`{server}`.docusign.net**, where `{server}` is the data center location of your production account (for example, **CA**, **NA2**, or **EU**)\n6. **Return URL template** - Return URL for your application to which DocuSign will redirect the user after signing the document. Set when you self host your application. You can use {sessionId}, {pathwayId}, {activityId} and {stakeholderId} variables to construct the URL, where variables will be replaced with actual values. Defaults to: \"https://goto.development.awell.health/?sessionId={sessionId}\". Remember that this URL MUST match the one you registered for your app in DocuSign settings. [See docs](https://developers.docusign.com/platform/configure-app/#redirect-uri) for more details.\n\nAlso, before working with **DocuSign** you should receive consent of the user to impersonate them with the API calls (even for your own account). Check the details on how to do that [on DocuSign docs](https://developers.docusign.com/platform/auth/consent/obtaining-individual-consent/). It's a ONE TIME operation and is required for API calls to work for specific client-scope-uri combination. Required params explained below:\n\n- `YOUR_REQUESTED_SCOPES`: This extension uses JWT Grant, so in place of `YOUR_REQUESTED_SCOPES` you MUST put at least `signature%20impersonation`.\n  - sample consent URL: https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation%20click.manage%20click.send&client_id=XYZ-123&redirect_uri=https://test.com\n\n## Custom Actions\n\n### Embedded signing\n\nEmbedded Signing gives users the ability to sign documents directly from Awell Hosted Pages using DocuSign's embedded signing feature. First an embedded signature request with a template is created and then a signing URL is generated for the signature request. Via the signing URL, we can let the user sign the request from within Awell.\n\nEmbedded signing behaves as a blocking action where the action is only completed when the signature request is effectively signed.\n\n**In order to add embedded signing, you need to add 2 actions to you care flow:**\n\n1. First, add the \"Create embedded signature request with template\" action. This action will create an embedded signature request based on a template and return a **sign URL**.\n2. Second, add the \"Embedded signing\" action. In this action you will have to configure the **sign URL** you got from the first action.\n\n**Please note that the signing URL generated in the first step is only valid for 5 minutes and is one-time only.** This means that from as soon as the first action is activated, the user has 5 minutes to complete the signing request. Loading a session by the user also means that sign url is loaded and refreshing the page will cause the link to expire. When the sign URL has expired, the document cannot be signed anymore and and the process would have to be repeated.\n",
     "changelog": "# DocuSign changelog\n"
@@ -115,6 +115,10 @@
     "readme": "---\ntitle: Sendgrid\ndescription: SendGrid is a cloud-based email delivery platform that provides services for sending and managing email campaigns, transactional emails, and other types of messages.\n---\n# Sendgrid\n\nSendGrid is a cloud-based email delivery platform that provides services for sending and managing email campaigns, transactional emails, and other types of messages.\n\n## Extension settings\n\nIn order to set up this extension, you will need to provide:\n\n1. An API key\n2. A from name\n3. A from email\n\n## Custom Actions\n\n### Send email\n\nAllows for sending a plain email to a recipient.\n\n### Send email with a template\n\nAllows for sending an email based on a template to a recipient. You can also insert variables so they are rendered in your template.\n\n### Add or update contact\n\nAllows adding or updating contacts. The contact to update will be determined only by the email field and any fields omitted from the request will remain as they were. A contact's ID cannot be used to update the contact.\n\nPlease note that custom fields need to have been already created if you wish to set their values for the contacts being upserted. To do this, please use the \"Create Custom Field Definition\" endpoint. They also can be created in **Marketing -> Custom Fields** section in Sendgrid.\n\n### Add and remove emails from suppression lists\n\nSuppression lists ([link on SendGrid's website](https://docs.sendgrid.com/api-reference/suppressions-suppressions/add-suppressions-to-a-suppression-group)) are unsubscribe groups. Use these actions to add an email address to any number of unsubscribe groups. You can apply a suppression add/remove to multiple groups by using comma-separated lists for the groups. Only a single email can be used. **This functionality is different from SendGrid's API, which allows multiple email addresses for a single group**.\n\n### Check an import status\n\nAllows user to check the status of contact import jobs when given a jobID. Statuses are either: `pending`, `completed`, `failed`, or `errored`.",
     "changelog": "# Sendgrid changelog\n\n## July 7, 2023\n\nAdded \"Add Email to Suppression Lists\" and \"Remove Email from Suppression Lists\" actions.\n\n## July 15, 2023\n\nUpdated \"Add or Update Contact\" acction to create a datapoint of the Job ID.\n\nAdded \"Check Import Status\" action.\n\n## July 27, 2023\n\nAdds \"Finished At\" data point to the importStatus action."
   },
+  "stripe": {
+    "readme": "---\ntitle: Stripe\ndescription: Stripe powers online and in-person payment processing and financial solutions for businesses of all sizes.\n---\n\n## Stripe\n\nStripe powers online and in-person payment processing and financial solutions for businesses of all sizes.\n\n## Extension settings\n\nFor the extension to function correctly, you must configure the following settings:\n\n- Secret key (test and live mode)\n- Publishable key (test and live mode)\n- Mode (\"Test\" or \"Live\")",
+    "changelog": "# Stripe changelog"
+  },
   "talkDesk": {
     "readme": "---\ntitle: Talkdesk\ndescription: Talkdesk is a cloud-based customer experience and contact center software company. It provides a platform that enables businesses to set up and manage their customer service and support operations.\n---\n# TalkDesk\n\nTalkdesk is a cloud-based customer experience and contact center software company. It provides a platform that enables businesses to set up and manage their customer service and support operations. Talkdesk offers a range of features and tools to streamline and enhance communication between businesses and their customers.\n\n## Setup\n\nTo set up the extension, you'll need your Talkdesk account name along with a client ID and client secret. Please ensure that the credentials you provide are associated with the necessary permissions, or \"scopes,\" to run the extension:\n\n- flows-interactions:start\n\n## Custom Actions\n\n### Trigger flow\n\nEnables the initiation of a Talkdesk flow directly from an Awell careflow. This feature triggers an interaction using the most recent published version of a specific Studio flow. You'll need to supply the ID of the flow and the data (as a JSON object) that you want to input into the flow.\n\nImportant: Please note that Talkdesk sets a restriction of up to two API requests per second (rps) for each account using their Flows API.\n\n[Click here](https://studio.talkdesk.com/docs/sending-notifications-to-contacts-via-api-request) to learn more about triggering flows via the Talkdesk API and here to read the [API docs](https://docs.talkdesk.com/reference/flows-api-ref).\n",
     "changelog": "# TalkDesk changelog\n"

package/dist/extensions/medplum/actions/createTask/config/fields.js

@@ -34,7 +34,7 @@ exports.fields = {
     },
     intent: {
         id: 'intent',
-        label: 'Mobile phone',
+        label: 'Intent',
         description: 'Indicates the "level" of actionability associated with the Task. Allowed values: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option',
         type: extensions_core_1.FieldType.STRING,
         required: true,

package/dist/extensions/medplum/actions/createTask/config/fields.js.map

@@ -1 +1 @@
-{"version":3,"file":"fields.js","sourceRoot":"","sources":["../../../../../../extensions/medplum/actions/createTask/config/fields.ts"],"names":[],"mappings":";;;AAAA,mEAAqE;AAErE,+DAAkE;AAErD,QAAA,MAAM,GAAG;IACpB,SAAS,EAAE;QACT,EAAE,EAAE,WAAW;QACf,KAAK,EAAE,YAAY;QACnB,WAAW,EAAE,8CAA8C;QAC3D,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,IAAI;KACf;IACD,SAAS,EAAE;QACT,EAAE,EAAE,WAAW;QACf,KAAK,EAAE,WAAW;QAClB,WAAW,EAAE,0CAA0C;QACvD,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,IAAI;KACf;IACD,WAAW,EAAE;QACX,EAAE,EAAE,aAAa;QACjB,KAAK,EAAE,kBAAkB;QACzB,WAAW,EAAE,oCAAoC;QACjD,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,KAAK;KAChB;IACD,MAAM,EAAE;QACN,EAAE,EAAE,QAAQ;QACZ,KAAK,EAAE,QAAQ;QACf,WAAW,EACT,gLAAgL;QAClL,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,IAAI;KACf;IACD,MAAM,EAAE;QACN,EAAE,EAAE,QAAQ;QACZ,KAAK,EAAE,cAAc;QACrB,WAAW,EACT,6LAA6L;QAC/L,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,IAAI;KACf;IACD,QAAQ,EAAE;QACR,EAAE,EAAE,UAAU;QACd,KAAK,EAAE,UAAU;QACjB,WAAW,EAAE,gDAAgD;QAC7D,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,KAAK;KAChB;IACD,OAAO,EAAE;QACP,EAAE,EAAE,SAAS;QACb,KAAK,EAAE,UAAU;QACjB,WAAW,EAAE,EAAE;QACf,IAAI,EAAE,2BAAS,CAAC,IAAI;QACpB,QAAQ,EAAE,KAAK;KAChB;IACD,aAAa,EAAE;QACb,EAAE,EAAE,eAAe;QACnB,KAAK,EAAE,gBAAgB;QACvB,WAAW,EAAE,kDAAkD;QAC/D,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,KAAK;KAChB;CAC8B,CAAA;AAEpB,QAAA,sBAAsB,GAAG,4BAErC,CAAA"}
+{"version":3,"file":"fields.js","sourceRoot":"","sources":["../../../../../../extensions/medplum/actions/createTask/config/fields.ts"],"names":[],"mappings":";;;AAAA,mEAAqE;AAErE,+DAAkE;AAErD,QAAA,MAAM,GAAG;IACpB,SAAS,EAAE;QACT,EAAE,EAAE,WAAW;QACf,KAAK,EAAE,YAAY;QACnB,WAAW,EAAE,8CAA8C;QAC3D,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,IAAI;KACf;IACD,SAAS,EAAE;QACT,EAAE,EAAE,WAAW;QACf,KAAK,EAAE,WAAW;QAClB,WAAW,EAAE,0CAA0C;QACvD,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,IAAI;KACf;IACD,WAAW,EAAE;QACX,EAAE,EAAE,aAAa;QACjB,KAAK,EAAE,kBAAkB;QACzB,WAAW,EAAE,oCAAoC;QACjD,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,KAAK;KAChB;IACD,MAAM,EAAE;QACN,EAAE,EAAE,QAAQ;QACZ,KAAK,EAAE,QAAQ;QACf,WAAW,EACT,gLAAgL;QAClL,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,IAAI;KACf;IACD,MAAM,EAAE;QACN,EAAE,EAAE,QAAQ;QACZ,KAAK,EAAE,QAAQ;QACf,WAAW,EACT,6LAA6L;QAC/L,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,IAAI;KACf;IACD,QAAQ,EAAE;QACR,EAAE,EAAE,UAAU;QACd,KAAK,EAAE,UAAU;QACjB,WAAW,EAAE,gDAAgD;QAC7D,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,KAAK;KAChB;IACD,OAAO,EAAE;QACP,EAAE,EAAE,SAAS;QACb,KAAK,EAAE,UAAU;QACjB,WAAW,EAAE,EAAE;QACf,IAAI,EAAE,2BAAS,CAAC,IAAI;QACpB,QAAQ,EAAE,KAAK;KAChB;IACD,aAAa,EAAE;QACb,EAAE,EAAE,eAAe;QACnB,KAAK,EAAE,gBAAgB;QACvB,WAAW,EAAE,kDAAkD;QAC/D,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,KAAK;KAChB;CAC8B,CAAA;AAEpB,QAAA,sBAAsB,GAAG,4BAErC,CAAA"}

package/dist/extensions/medplum/actions/getAppointment/config/dataPoints.d.ts

@@ -1,6 +1,6 @@
 export declare const dataPoints: {
     appointmentData: {
         key: string;
-        valueType: "string";
+        valueType: "json";
     };
 };

package/dist/extensions/medplum/actions/getAppointment/config/dataPoints.js

@@ -4,7 +4,7 @@ exports.dataPoints = void 0;
 exports.dataPoints = {
     appointmentData: {
         key: 'appointmentData',
-        valueType: 'string',
+        valueType: 'json',
     },
 };
 //# sourceMappingURL=dataPoints.js.map

package/dist/extensions/medplum/actions/getAppointment/config/dataPoints.js.map

@@ -1 +1 @@
-{"version":3,"file":"dataPoints.js","sourceRoot":"","sources":["../../../../../../extensions/medplum/actions/getAppointment/config/dataPoints.ts"],"names":[],"mappings":";;;AAEa,QAAA,UAAU,GAAG;IACxB,eAAe,EAAE;QACf,GAAG,EAAE,iBAAiB;QACtB,SAAS,EAAE,QAAQ;KACpB;CAC4C,CAAA"}
+{"version":3,"file":"dataPoints.js","sourceRoot":"","sources":["../../../../../../extensions/medplum/actions/getAppointment/config/dataPoints.ts"],"names":[],"mappings":";;;AAEa,QAAA,UAAU,GAAG;IACxB,eAAe,EAAE;QACf,GAAG,EAAE,iBAAiB;QACtB,SAAS,EAAE,MAAM;KAClB;CAC4C,CAAA"}

package/dist/extensions/medplum/actions/getAppointment/getAppointment.js

@@ -18,11 +18,6 @@ exports.getAppointment = {
             payload,
         });
         const res = await medplumSdk.readResource('Appointment', input.appointmentId);
-        /**
-         * TODO:
-         * Either create specific data points and pick from the appointment object what we need OR
-         * store the full object and allow introspection and picking the values the builder needs in Awell Studio.
-         */
         await onComplete({
             data_points: {
                 appointmentData: JSON.stringify(res),

package/dist/extensions/medplum/actions/getAppointment/getAppointment.js.map

@@ -1 +1 @@
-{"version":3,"file":"getAppointment.js","sourceRoot":"","sources":["../../../../../extensions/medplum/actions/getAppointment/getAppointment.ts"],"names":[],"mappings":";;;AAAA,mEAAqE;AAErE,qCAAqE;AACrE,uCAAwD;AAE3C,QAAA,cAAc,GAIvB;IACF,GAAG,EAAE,gBAAgB;IACrB,QAAQ,EAAE,0BAAQ,CAAC,gBAAgB;IACnC,KAAK,EAAE,iBAAiB;IACxB,WAAW,EAAE,2CAA2C;IACxD,MAAM,EAAN,eAAM;IACN,WAAW,EAAE,IAAI;IACjB,UAAU,EAAV,mBAAU;IACV,iBAAiB,EAAE,KAAK,EAAE,OAAO,EAAE,UAAU,EAAE,OAAO,EAAiB,EAAE;QACvE,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,UAAU,EAAE,GAAG,MAAM,IAAA,kCAA0B,EAAC;YACrE,YAAY,EAAE,+BAAsB;YACpC,OAAO;SACR,CAAC,CAAA;QAEF,MAAM,GAAG,GAAG,MAAM,UAAU,CAAC,YAAY,CACvC,aAAa,EACb,KAAK,CAAC,aAAa,CACpB,CAAA;QAED;;;;WAIG;QACH,MAAM,UAAU,CAAC;YACf,WAAW,EAAE;gBACX,eAAe,EAAE,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC;aACrC;SACF,CAAC,CAAA;IACJ,CAAC;CACF,CAAA"}
+{"version":3,"file":"getAppointment.js","sourceRoot":"","sources":["../../../../../extensions/medplum/actions/getAppointment/getAppointment.ts"],"names":[],"mappings":";;;AAAA,mEAAqE;AAErE,qCAAqE;AACrE,uCAAwD;AAE3C,QAAA,cAAc,GAIvB;IACF,GAAG,EAAE,gBAAgB;IACrB,QAAQ,EAAE,0BAAQ,CAAC,gBAAgB;IACnC,KAAK,EAAE,iBAAiB;IACxB,WAAW,EAAE,2CAA2C;IACxD,MAAM,EAAN,eAAM;IACN,WAAW,EAAE,IAAI;IACjB,UAAU,EAAV,mBAAU;IACV,iBAAiB,EAAE,KAAK,EAAE,OAAO,EAAE,UAAU,EAAE,OAAO,EAAiB,EAAE;QACvE,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,UAAU,EAAE,GAAG,MAAM,IAAA,kCAA0B,EAAC;YACrE,YAAY,EAAE,+BAAsB;YACpC,OAAO;SACR,CAAC,CAAA;QAEF,MAAM,GAAG,GAAG,MAAM,UAAU,CAAC,YAAY,CACvC,aAAa,EACb,KAAK,CAAC,aAAa,CACpB,CAAA;QAED,MAAM,UAAU,CAAC;YACf,WAAW,EAAE;gBACX,eAAe,EAAE,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC;aACrC;SACF,CAAC,CAAA;IACJ,CAAC;CACF,CAAA"}

package/dist/extensions/medplum/actions/getPatient/config/dataPoints.d.ts

@@ -1,6 +1,6 @@
 export declare const dataPoints: {
     patientData: {
         key: string;
-        valueType: "string";
+        valueType: "json";
     };
 };

package/dist/extensions/medplum/actions/getPatient/config/dataPoints.js

@@ -4,7 +4,7 @@ exports.dataPoints = void 0;
 exports.dataPoints = {
     patientData: {
         key: 'patientData',
-        valueType: 'string',
+        valueType: 'json',
     },
 };
 //# sourceMappingURL=dataPoints.js.map

package/dist/extensions/medplum/actions/getPatient/config/dataPoints.js.map

@@ -1 +1 @@
-{"version":3,"file":"dataPoints.js","sourceRoot":"","sources":["../../../../../../extensions/medplum/actions/getPatient/config/dataPoints.ts"],"names":[],"mappings":";;;AAEa,QAAA,UAAU,GAAG;IACxB,WAAW,EAAE;QACX,GAAG,EAAE,aAAa;QAClB,SAAS,EAAE,QAAQ;KACpB;CAC4C,CAAA"}
+{"version":3,"file":"dataPoints.js","sourceRoot":"","sources":["../../../../../../extensions/medplum/actions/getPatient/config/dataPoints.ts"],"names":[],"mappings":";;;AAEa,QAAA,UAAU,GAAG;IACxB,WAAW,EAAE;QACX,GAAG,EAAE,aAAa;QAClB,SAAS,EAAE,MAAM;KAClB;CAC4C,CAAA"}

package/dist/extensions/medplum/actions/getPatient/getPatient.js

@@ -18,11 +18,6 @@ exports.getPatient = {
             payload,
         });
         const res = await medplumSdk.readResource('Patient', input.patientId);
-        /**
-         * TODO:
-         * Either create specific data points and pick from the patient object what we need OR
-         * store the full object and allow introspection and picking the values the builder needs in Awell Studio.
-         */
         await onComplete({
             data_points: {
                 patientData: JSON.stringify(res),

package/dist/extensions/medplum/actions/getPatient/getPatient.js.map

@@ -1 +1 @@
-{"version":3,"file":"getPatient.js","sourceRoot":"","sources":["../../../../../extensions/medplum/actions/getPatient/getPatient.ts"],"names":[],"mappings":";;;AAAA,mEAAqE;AAErE,qCAAqE;AACrE,uCAAwD;AAE3C,QAAA,UAAU,GAInB;IACF,GAAG,EAAE,YAAY;IACjB,QAAQ,EAAE,0BAAQ,CAAC,gBAAgB;IACnC,KAAK,EAAE,aAAa;IACpB,WAAW,EAAE,uCAAuC;IACpD,MAAM,EAAN,eAAM;IACN,WAAW,EAAE,IAAI;IACjB,UAAU,EAAV,mBAAU;IACV,iBAAiB,EAAE,KAAK,EAAE,OAAO,EAAE,UAAU,EAAE,OAAO,EAAiB,EAAE;QACvE,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,UAAU,EAAE,GAAG,MAAM,IAAA,kCAA0B,EAAC;YACrE,YAAY,EAAE,+BAAsB;YACpC,OAAO;SACR,CAAC,CAAA;QAEF,MAAM,GAAG,GAAG,MAAM,UAAU,CAAC,YAAY,CAAC,SAAS,EAAE,KAAK,CAAC,SAAS,CAAC,CAAA;QAErE;;;;WAIG;QACH,MAAM,UAAU,CAAC;YACf,WAAW,EAAE;gBACX,WAAW,EAAE,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC;aACjC;SACF,CAAC,CAAA;IACJ,CAAC;CACF,CAAA"}
+{"version":3,"file":"getPatient.js","sourceRoot":"","sources":["../../../../../extensions/medplum/actions/getPatient/getPatient.ts"],"names":[],"mappings":";;;AAAA,mEAAqE;AAErE,qCAAqE;AACrE,uCAAwD;AAE3C,QAAA,UAAU,GAInB;IACF,GAAG,EAAE,YAAY;IACjB,QAAQ,EAAE,0BAAQ,CAAC,gBAAgB;IACnC,KAAK,EAAE,aAAa;IACpB,WAAW,EAAE,uCAAuC;IACpD,MAAM,EAAN,eAAM;IACN,WAAW,EAAE,IAAI;IACjB,UAAU,EAAV,mBAAU;IACV,iBAAiB,EAAE,KAAK,EAAE,OAAO,EAAE,UAAU,EAAE,OAAO,EAAiB,EAAE;QACvE,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,UAAU,EAAE,GAAG,MAAM,IAAA,kCAA0B,EAAC;YACrE,YAAY,EAAE,+BAAsB;YACpC,OAAO;SACR,CAAC,CAAA;QAEF,MAAM,GAAG,GAAG,MAAM,UAAU,CAAC,YAAY,CAAC,SAAS,EAAE,KAAK,CAAC,SAAS,CAAC,CAAA;QAErE,MAAM,UAAU,CAAC;YACf,WAAW,EAAE;gBACX,WAAW,EAAE,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC;aACjC;SACF,CAAC,CAAA;IACJ,CAAC;CACF,CAAA"}

package/dist/extensions/medplum/actions/index.d.ts

@@ -4,3 +4,4 @@ export { getAppointment } from './getAppointment';
 export { executeBot } from './executeBot';
 export { createTask } from './createTask';
 export { createServiceRequest } from './createServiceRequest';
+export { submitQuestionnaireResponse } from './submitQuestionnaireResponse';

package/dist/extensions/medplum/actions/index.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.createServiceRequest = exports.createTask = exports.executeBot = exports.getAppointment = exports.createPatient = exports.getPatient = void 0;
+exports.submitQuestionnaireResponse = exports.createServiceRequest = exports.createTask = exports.executeBot = exports.getAppointment = exports.createPatient = exports.getPatient = void 0;
 var getPatient_1 = require("./getPatient");
 Object.defineProperty(exports, "getPatient", { enumerable: true, get: function () { return getPatient_1.getPatient; } });
 var createPatient_1 = require("./createPatient");
@@ -13,4 +13,6 @@ var createTask_1 = require("./createTask");
 Object.defineProperty(exports, "createTask", { enumerable: true, get: function () { return createTask_1.createTask; } });
 var createServiceRequest_1 = require("./createServiceRequest");
 Object.defineProperty(exports, "createServiceRequest", { enumerable: true, get: function () { return createServiceRequest_1.createServiceRequest; } });
+var submitQuestionnaireResponse_1 = require("./submitQuestionnaireResponse");
+Object.defineProperty(exports, "submitQuestionnaireResponse", { enumerable: true, get: function () { return submitQuestionnaireResponse_1.submitQuestionnaireResponse; } });
 //# sourceMappingURL=index.js.map

package/dist/extensions/medplum/actions/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../extensions/medplum/actions/index.ts"],"names":[],"mappings":";;;AAAA,2CAAyC;AAAhC,wGAAA,UAAU,OAAA;AACnB,iDAA+C;AAAtC,8GAAA,aAAa,OAAA;AACtB,mDAAiD;AAAxC,gHAAA,cAAc,OAAA;AACvB,2CAAyC;AAAhC,wGAAA,UAAU,OAAA;AACnB,2CAAyC;AAAhC,wGAAA,UAAU,OAAA;AACnB,+DAA6D;AAApD,4HAAA,oBAAoB,OAAA"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../extensions/medplum/actions/index.ts"],"names":[],"mappings":";;;AAAA,2CAAyC;AAAhC,wGAAA,UAAU,OAAA;AACnB,iDAA+C;AAAtC,8GAAA,aAAa,OAAA;AACtB,mDAAiD;AAAxC,gHAAA,cAAc,OAAA;AACvB,2CAAyC;AAAhC,wGAAA,UAAU,OAAA;AACnB,2CAAyC;AAAhC,wGAAA,UAAU,OAAA;AACnB,+DAA6D;AAApD,4HAAA,oBAAoB,OAAA;AAC7B,6EAA2E;AAAlE,0IAAA,2BAA2B,OAAA"}

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/config/dataPoints.d.ts

@@ -0,0 +1,6 @@
+export declare const dataPoints: {
+    questionnnaireResponseId: {
+        key: string;
+        valueType: "string";
+    };
+};

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/config/dataPoints.js

@@ -0,0 +1,10 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.dataPoints = void 0;
+exports.dataPoints = {
+    questionnnaireResponseId: {
+        key: 'questionnnaireResponseId',
+        valueType: 'string',
+    },
+};
+//# sourceMappingURL=dataPoints.js.map

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/config/dataPoints.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"dataPoints.js","sourceRoot":"","sources":["../../../../../../extensions/medplum/actions/submitQuestionnaireResponse/config/dataPoints.ts"],"names":[],"mappings":";;;AAEa,QAAA,UAAU,GAAG;IACxB,wBAAwB,EAAE;QACxB,GAAG,EAAE,0BAA0B;QAC/B,SAAS,EAAE,QAAQ;KACpB;CAC4C,CAAA"}

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/config/fields.d.ts

@@ -0,0 +1,18 @@
+import { FieldType } from '@awell-health/extensions-core';
+import { z } from 'zod';
+export declare const fields: {
+    patientId: {
+        id: string;
+        label: string;
+        description: string;
+        type: FieldType.STRING;
+        required: true;
+    };
+};
+export declare const FieldsValidationSchema: z.ZodObject<{
+    patientId: z.ZodString;
+}, "strip", z.ZodTypeAny, {
+    patientId: string;
+}, {
+    patientId: string;
+}>;

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/config/fields.js

@@ -0,0 +1,18 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.FieldsValidationSchema = exports.fields = void 0;
+const extensions_core_1 = require("@awell-health/extensions-core");
+const zod_1 = require("zod");
+exports.fields = {
+    patientId: {
+        id: 'patientId',
+        label: 'Patient ID',
+        description: 'The identifier of the patient in Medplum to assign the response to',
+        type: extensions_core_1.FieldType.STRING,
+        required: true,
+    },
+};
+exports.FieldsValidationSchema = zod_1.z.object({
+    patientId: zod_1.z.string().min(1),
+});
+//# sourceMappingURL=fields.js.map

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/config/fields.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"fields.js","sourceRoot":"","sources":["../../../../../../extensions/medplum/actions/submitQuestionnaireResponse/config/fields.ts"],"names":[],"mappings":";;;AAAA,mEAAqE;AACrE,6BAAwC;AAE3B,QAAA,MAAM,GAAG;IACpB,SAAS,EAAE;QACT,EAAE,EAAE,WAAW;QACf,KAAK,EAAE,YAAY;QACnB,WAAW,EACT,oEAAoE;QACtE,IAAI,EAAE,2BAAS,CAAC,MAAM;QACtB,QAAQ,EAAE,IAAI;KACf;CAC8B,CAAA;AAEpB,QAAA,sBAAsB,GAAG,OAAC,CAAC,MAAM,CAAC;IAC7C,SAAS,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;CACqB,CAAC,CAAA"}

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/config/index.d.ts

@@ -0,0 +1,2 @@
+export * from './dataPoints';
+export * from './fields';

package/dist/extensions/{awell/v1/gql → medplum/actions/submitQuestionnaireResponse/config}/index.js

@@ -14,6 +14,6 @@ var __exportStar = (this && this.__exportStar) || function(m, exports) {
     for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-__exportStar(require("./fragment-masking"), exports);
-__exportStar(require("./gql"), exports);
+__exportStar(require("./dataPoints"), exports);
+__exportStar(require("./fields"), exports);
 //# sourceMappingURL=index.js.map

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/config/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../../../extensions/medplum/actions/submitQuestionnaireResponse/config/index.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;AAAA,+CAA4B;AAC5B,2CAAwB"}

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/index.d.ts

@@ -0,0 +1 @@
+export { submitQuestionnaireResponse } from './submitQuestionnaireResponse';

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/index.js

@@ -0,0 +1,6 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.submitQuestionnaireResponse = void 0;
+var submitQuestionnaireResponse_1 = require("./submitQuestionnaireResponse");
+Object.defineProperty(exports, "submitQuestionnaireResponse", { enumerable: true, get: function () { return submitQuestionnaireResponse_1.submitQuestionnaireResponse; } });
+//# sourceMappingURL=index.js.map

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../../extensions/medplum/actions/submitQuestionnaireResponse/index.ts"],"names":[],"mappings":";;;AAAA,6EAA2E;AAAlE,0IAAA,2BAA2B,OAAA"}

package/dist/extensions/medplum/actions/submitQuestionnaireResponse/submitQuestionnaireResponse.d.ts

@@ -0,0 +1,4 @@
+import { type Action } from '@awell-health/extensions-core';
+import { type settings } from '../../settings';
+import { fields, dataPoints } from './config';
+export declare const submitQuestionnaireResponse: Action<typeof fields, typeof settings, keyof typeof dataPoints>;