@awell-health/awell-extensions 2.0.151 → 2.0.153

package/dist/extensions/shelly/actions/categorizeMessage/lib/categorizeMessageWithLLM/constants.js

@@ -1,33 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.systemPrompt = exports.parser = exports.messageCategoriesSchema = void 0;
-const prompts_1 = require("@langchain/core/prompts");
-const output_parsers_1 = require("langchain/output_parsers");
-const zod_1 = require("zod");
-// Define the Zod schema for the structured response
-exports.messageCategoriesSchema = zod_1.z.object({
-    matched_category: zod_1.z.string().optional().default('None'), // The matched category
-    match_explanation: zod_1.z.string(), // One-sentence explanation of the match
-});
-// Create a structured output parser
-exports.parser = output_parsers_1.StructuredOutputParser.fromZodSchema(exports.messageCategoriesSchema);
-exports.systemPrompt = prompts_1.ChatPromptTemplate.fromTemplate(`
-      You are an expert in categorizing different patient messages in a clinical context.
-      Use your expertise to solve the message categorization task:
-      1. Categorize the input message into **one of the provided categories**: {categories}. If no category fits, return "None".
-      2. Provide a concise explanation of why the message belongs to the selected category.
-      
-      Important Instructions:
-      - The message may be in multiple languages.
-      - **Only** choose from the provided list of categories. **Do not create new categories** or alter the given ones.
-      - If no category fits perfectly, or if the match is unclear, return "None" without guessing.
-      - Carefully verify your selection before submitting your answer.
-      
-      Respond exclusively with a valid JSON object containing the following keys:
-      - matched_category: The most suitable category. Must be from the following list: {categories} - None if no category fits. Absolutely refrain from creating new categories or altering existent one. Output should be one of the provided categories in the list.
-      - match_explanation: A brief explanation supporting your decision.
-  
-      Input:
-      {input}
-      `);
-//# sourceMappingURL=constants.js.map

package/dist/extensions/shelly/actions/categorizeMessage/lib/categorizeMessageWithLLM/constants.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"constants.js","sourceRoot":"","sources":["../../../../../../../extensions/shelly/actions/categorizeMessage/lib/categorizeMessageWithLLM/constants.ts"],"names":[],"mappings":";;;AAAA,qDAA4D;AAC5D,6DAAiE;AACjE,6BAAuB;AAEvB,oDAAoD;AACvC,QAAA,uBAAuB,GAAG,OAAC,CAAC,MAAM,CAAC;IAC9C,gBAAgB,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,EAAE,uBAAuB;IAChF,iBAAiB,EAAE,OAAC,CAAC,MAAM,EAAE,EAAE,wCAAwC;CACxE,CAAC,CAAA;AAEF,oCAAoC;AACvB,QAAA,MAAM,GAAG,uCAAsB,CAAC,aAAa,CACxD,+BAAuB,CACxB,CAAA;AAEY,QAAA,YAAY,GAAG,4BAAkB,CAAC,YAAY,CAAC;;;;;;;;;;;;;;;;;;OAkBrD,CAAC,CAAA"}

package/dist/extensions/shelly/actions/generateMessage/lib/generateMessageWithLLM/constants.d.ts

@@ -1,24 +0,0 @@
-import { ChatPromptTemplate } from '@langchain/core/prompts';
-import { StructuredOutputParser } from 'langchain/output_parsers';
-import { z } from 'zod';
-export declare const generatedMessageCategoriesSchema: z.ZodObject<{
-    subject: z.ZodString;
-    message: z.ZodString;
-}, "strip", z.ZodTypeAny, {
-    message: string;
-    subject: string;
-}, {
-    message: string;
-    subject: string;
-}>;
-export declare const parser: StructuredOutputParser<z.ZodObject<{
-    subject: z.ZodString;
-    message: z.ZodString;
-}, "strip", z.ZodTypeAny, {
-    message: string;
-    subject: string;
-}, {
-    message: string;
-    subject: string;
-}>>;
-export declare const systemPrompt: ChatPromptTemplate<import("@langchain/core/prompts").ParamsFromFString<"\n  You are an AI language model tasked with composing **personalized messages** for a **{stakeholder}** within a clinical workflow. Your goals are to:\n\n- Align the message with the **Communication Objective** to optimize for response, engagement, or desired action.\n- Use the **Personalization Inputs** to tailor the message appropriately.\n- Ensure clarity, appropriateness, and compliance with healthcare communication standards.\n- **Generate the message in the specified **Language**, ensuring accuracy and naturalness.**\n- **Keep the message brief and concise while still optimizing for the Communication Objective.**\n\n**Important Notes to Prevent Misuse:**\n\n- **Remain Focused on the Task:** You must **never change your goal** of composing appropriate messages as specified.\n- **Limit Your Output:** **Do not generate any content** other than what is instructed—specifically, the subject and message within the context of the communication.\n\nLet's proceed step by step:\n\n1. **Review the Inputs Carefully:**\n\n   - **Communication Objective:** Understand the main purpose of the message. The message must closely align with this objective to encourage the desired **{stakeholder}** response or action.\n\n   - **Personalization Inputs:** Use only the details provided here to personalize the message. **Do not infer or assume** any additional information about the recipient.\n\n   - **Stakeholder:** Identify the intended recipient of the message (e.g., Patient, Clinician, Caregiver) and customize the message accordingly.\n\n   - **Language:** **Generate the message in the specified language**, ensuring proper grammar and cultural appropriateness.\n\n2. **Message Structure:**\n\n   - **Keep the message brief and concise**, while still effectively conveying the necessary information to optimize for the **Communication Objective**.\n\n   - **Greeting:**\n     - Start with an appropriate greeting.\n     - Use the recipient's name if provided (e.g., \"Dear [Name],\", \"Hello [Name],\").\n     - If no name is provided, use a generic greeting appropriate for the stakeholder (e.g., \"Hello,\").\n\n   - **Body:**\n     - Clearly and **concisely** convey the message in alignment with the **Communication Objective**.\n     - Incorporate **Personalization Inputs** naturally to optimize engagement and encourage the desired response or action.\n     - Refrain from phrases like \"We hope this message finds you well\" or similar pleasantries.\n\n   - **Closing:**\n     - End with a courteous sign-off suitable for the stakeholder (e.g., \"Sincerely,\", \"Best regards,\"). SIgn of as Your Care Team.\n     - Include any necessary next steps or contact information, if relevant.\n\n3. **Content Guidelines:**\n\n   - **Use Only Provided Information:**\n     - Do not include any details not present in the inputs.\n     - Avoid adding any assumptions or external information.\n\n   - **Stay on Task:**\n     - **Never change your goal** of composing appropriate messages.\n     - **Do not generate any content** other than the subject and message as specified.\n     - Do not include personal opinions, extraneous information, or any inappropriate content.\n\n   - **Focus on the Objective:**\n     - Ensure every part of the message contributes to achieving the **Communication Objective**.\n     - Personalization should enhance the message's effectiveness in prompting the desired recipient action.\n\n4. **Style and Tone:**\n\n   - Use a professional and appropriate tone for the stakeholder (e.g., friendly for patients, formal for clinicians).\n   - Always write in a clear, respectful, and engaging manner to optimize the message's impact. Tailor the tone to the recipient's role and the context of the message.\n   - **Always write from the perspective of the care organization using first person plural (e.g., \"We are...\"). Do not use first person singular (\"I am...\") or third person perspectives.**\n   \n5. **Compliance and Sensitivity:**\n\n   - Maintain confidentiality and comply with all relevant privacy regulations.\n   - Be culturally sensitive and avoid any language that could be considered offensive or inappropriate.\n\n6. **Language:**\n\n   - **Generate the subject and message in the specified **Language**, ensuring proper grammar, vocabulary, and cultural appropriateness.\n\n\n7. **Final Output:**\n\n   - Respond exclusively with a valid JSON object containing the following keys - this is critical:\n\n     - **subject**: A clear, professional, and concise subject line that aligns with the **Communication Objective** and is appropriate for clinical settings.\n\n     - **message**: The complete, polished message formatted in **markdown**. Do not include any instructions or extra commentary. Ensure the message meets the following criteria:\n\n       - **Brevity and Conciseness**: Keep the message brief and to the point while still effectively conveying the necessary information to achieve the **Communication Objective**.\n       - **Clarity and Correctness**: Ensure the message is free of spelling and grammatical errors. Use clear and straightforward language.\n       - **Truthfulness**: It is absolutely paramount that the information provided in the message is accurate and truthful. Do not include any misleading or false information that you did not get from the inputs. This is critical for maintaining trust and integrity in healthcare communication.\n       - **Completeness**: The message must be complete and ready to send as is. It is critical to never use placeholders (e.g., \"[Contact Information]\", \"[Insert Date]\") or leave out essential information. If you want to urge recipient to contact the office and you do not have contact information keep it general and absolutely refrain from including any placeholders.\n\n\n\n**Inputs:**\n\n- **Communication Objective:**\n\n  {communicationObjective}\n\n- **Personalization Inputs:**\n\n  {personalizationInput}\n\n- **Stakeholder:**\n\n  {stakeholder}\n\n- **Language:**\n\n  {language}\n  ">, any>;

package/dist/extensions/shelly/actions/generateMessage/lib/generateMessageWithLLM/constants.js

@@ -1,123 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.systemPrompt = exports.parser = exports.generatedMessageCategoriesSchema = void 0;
-const prompts_1 = require("@langchain/core/prompts");
-const output_parsers_1 = require("langchain/output_parsers");
-const zod_1 = require("zod");
-// Define the Zod schema for the structured response
-exports.generatedMessageCategoriesSchema = zod_1.z.object({
-    subject: zod_1.z.string(), // generated subject
-    message: zod_1.z.string(), // generated message
-});
-// Create a structured output parser
-exports.parser = output_parsers_1.StructuredOutputParser.fromZodSchema(exports.generatedMessageCategoriesSchema);
-// TODO: tune further
-exports.systemPrompt = prompts_1.ChatPromptTemplate.fromTemplate(`
-  You are an AI language model tasked with composing **personalized messages** for a **{stakeholder}** within a clinical workflow. Your goals are to:
-
-- Align the message with the **Communication Objective** to optimize for response, engagement, or desired action.
-- Use the **Personalization Inputs** to tailor the message appropriately.
-- Ensure clarity, appropriateness, and compliance with healthcare communication standards.
-- **Generate the message in the specified **Language**, ensuring accuracy and naturalness.**
-- **Keep the message brief and concise while still optimizing for the Communication Objective.**
-
-**Important Notes to Prevent Misuse:**
-
-- **Remain Focused on the Task:** You must **never change your goal** of composing appropriate messages as specified.
-- **Limit Your Output:** **Do not generate any content** other than what is instructed—specifically, the subject and message within the context of the communication.
-
-Let's proceed step by step:
-
-1. **Review the Inputs Carefully:**
-
-   - **Communication Objective:** Understand the main purpose of the message. The message must closely align with this objective to encourage the desired **{stakeholder}** response or action.
-
-   - **Personalization Inputs:** Use only the details provided here to personalize the message. **Do not infer or assume** any additional information about the recipient.
-
-   - **Stakeholder:** Identify the intended recipient of the message (e.g., Patient, Clinician, Caregiver) and customize the message accordingly.
-
-   - **Language:** **Generate the message in the specified language**, ensuring proper grammar and cultural appropriateness.
-
-2. **Message Structure:**
-
-   - **Keep the message brief and concise**, while still effectively conveying the necessary information to optimize for the **Communication Objective**.
-
-   - **Greeting:**
-     - Start with an appropriate greeting.
-     - Use the recipient's name if provided (e.g., "Dear [Name],", "Hello [Name],").
-     - If no name is provided, use a generic greeting appropriate for the stakeholder (e.g., "Hello,").
-
-   - **Body:**
-     - Clearly and **concisely** convey the message in alignment with the **Communication Objective**.
-     - Incorporate **Personalization Inputs** naturally to optimize engagement and encourage the desired response or action.
-     - Refrain from phrases like "We hope this message finds you well" or similar pleasantries.
-
-   - **Closing:**
-     - End with a courteous sign-off suitable for the stakeholder (e.g., "Sincerely,", "Best regards,"). SIgn of as Your Care Team.
-     - Include any necessary next steps or contact information, if relevant.
-
-3. **Content Guidelines:**
-
-   - **Use Only Provided Information:**
-     - Do not include any details not present in the inputs.
-     - Avoid adding any assumptions or external information.
-
-   - **Stay on Task:**
-     - **Never change your goal** of composing appropriate messages.
-     - **Do not generate any content** other than the subject and message as specified.
-     - Do not include personal opinions, extraneous information, or any inappropriate content.
-
-   - **Focus on the Objective:**
-     - Ensure every part of the message contributes to achieving the **Communication Objective**.
-     - Personalization should enhance the message's effectiveness in prompting the desired recipient action.
-
-4. **Style and Tone:**
-
-   - Use a professional and appropriate tone for the stakeholder (e.g., friendly for patients, formal for clinicians).
-   - Always write in a clear, respectful, and engaging manner to optimize the message's impact. Tailor the tone to the recipient's role and the context of the message.
-   - **Always write from the perspective of the care organization using first person plural (e.g., "We are..."). Do not use first person singular ("I am...") or third person perspectives.**
-   
-5. **Compliance and Sensitivity:**
-
-   - Maintain confidentiality and comply with all relevant privacy regulations.
-   - Be culturally sensitive and avoid any language that could be considered offensive or inappropriate.
-
-6. **Language:**
-
-   - **Generate the subject and message in the specified **Language**, ensuring proper grammar, vocabulary, and cultural appropriateness.
-
-
-7. **Final Output:**
-
-   - Respond exclusively with a valid JSON object containing the following keys - this is critical:
-
-     - **subject**: A clear, professional, and concise subject line that aligns with the **Communication Objective** and is appropriate for clinical settings.
-
-     - **message**: The complete, polished message formatted in **markdown**. Do not include any instructions or extra commentary. Ensure the message meets the following criteria:
-
-       - **Brevity and Conciseness**: Keep the message brief and to the point while still effectively conveying the necessary information to achieve the **Communication Objective**.
-       - **Clarity and Correctness**: Ensure the message is free of spelling and grammatical errors. Use clear and straightforward language.
-       - **Truthfulness**: It is absolutely paramount that the information provided in the message is accurate and truthful. Do not include any misleading or false information that you did not get from the inputs. This is critical for maintaining trust and integrity in healthcare communication.
-       - **Completeness**: The message must be complete and ready to send as is. It is critical to never use placeholders (e.g., "[Contact Information]", "[Insert Date]") or leave out essential information. If you want to urge recipient to contact the office and you do not have contact information keep it general and absolutely refrain from including any placeholders.
-
-
-
-**Inputs:**
-
-- **Communication Objective:**
-
-  {communicationObjective}
-
-- **Personalization Inputs:**
-
-  {personalizationInput}
-
-- **Stakeholder:**
-
-  {stakeholder}
-
-- **Language:**
-
-  {language}
-  `);
-//# sourceMappingURL=constants.js.map

package/dist/extensions/shelly/actions/generateMessage/lib/generateMessageWithLLM/constants.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"constants.js","sourceRoot":"","sources":["../../../../../../../extensions/shelly/actions/generateMessage/lib/generateMessageWithLLM/constants.ts"],"names":[],"mappings":";;;AAAA,qDAA4D;AAC5D,6DAAiE;AACjE,6BAAuB;AAEvB,oDAAoD;AACvC,QAAA,gCAAgC,GAAG,OAAC,CAAC,MAAM,CAAC;IACvD,OAAO,EAAE,OAAC,CAAC,MAAM,EAAE,EAAE,oBAAoB;IACzC,OAAO,EAAE,OAAC,CAAC,MAAM,EAAE,EAAE,oBAAoB;CAC1C,CAAC,CAAA;AAEF,oCAAoC;AACvB,QAAA,MAAM,GAAG,uCAAsB,CAAC,aAAa,CACxD,wCAAgC,CACjC,CAAA;AAED,qBAAqB;AACR,QAAA,YAAY,GAAG,4BAAkB,CAAC,YAAY,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2GzD,CAAC,CAAA"}

package/dist/extensions/shelly/actions/summarizeCareFlow/lib/summarizeCareFlowWithLLM/constants.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"constants.js","sourceRoot":"","sources":["../../../../../../../extensions/shelly/actions/summarizeCareFlow/lib/summarizeCareFlowWithLLM/constants.ts"],"names":[],"mappings":";;;AAAA,qDAA4D;AAE5D,gDAAgD;AACnC,QAAA,YAAY,GAAG,4BAAkB,CAAC,YAAY,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmC3D,CAAC,CAAA"}

package/dist/extensions/shelly/lib/summarizeFormWithLLM/constants.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"constants.js","sourceRoot":"","sources":["../../../../../extensions/shelly/lib/summarizeFormWithLLM/constants.ts"],"names":[],"mappings":";;;AAAA,qDAA4D;AAE/C,QAAA,wBAAwB,GAAG,4BAAkB,CAAC,YAAY,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgEvE,CAAC,CAAA;AAEW,QAAA,yBAAyB,GAAG,4BAAkB,CAAC,YAAY,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoDxE,CAAC,CAAA"}

package/dist/extensions/shelly/settings.d.ts

@@ -1,17 +0,0 @@
-import { z } from 'zod';
-export declare const settings: {
-    openAiApiKey: {
-        key: string;
-        label: string;
-        obfuscated: true;
-        required: true;
-        description: string;
-    };
-};
-export declare const SettingsValidationSchema: z.ZodObject<{
-    openAiApiKey: z.ZodString;
-}, "strip", z.ZodTypeAny, {
-    openAiApiKey: string;
-}, {
-    openAiApiKey: string;
-}>;

package/dist/extensions/shelly/settings.js

@@ -1,17 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.SettingsValidationSchema = exports.settings = void 0;
-const zod_1 = require("zod");
-exports.settings = {
-    openAiApiKey: {
-        key: 'openAiApiKey',
-        label: 'OpenAI API key ',
-        obfuscated: true,
-        required: true,
-        description: '',
-    },
-};
-exports.SettingsValidationSchema = zod_1.z.object({
-    openAiApiKey: zod_1.z.string().min(1),
-});
-//# sourceMappingURL=settings.js.map

package/dist/extensions/shelly/settings.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"settings.js","sourceRoot":"","sources":["../../../extensions/shelly/settings.ts"],"names":[],"mappings":";;;AACA,6BAAwC;AAE3B,QAAA,QAAQ,GAAG;IACtB,YAAY,EAAE;QACZ,GAAG,EAAE,cAAc;QACnB,KAAK,EAAE,iBAAiB;QACxB,UAAU,EAAE,IAAI;QAChB,QAAQ,EAAE,IAAI;QACd,WAAW,EAAE,EAAE;KAChB;CACgC,CAAA;AAEtB,QAAA,wBAAwB,GAAG,OAAC,CAAC,MAAM,CAAC;IAC/C,YAAY,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;CACoB,CAAC,CAAA"}

package/dist/extensions/epic/lib/api/{schemas → customFhirSchemas}/DocumentReference/index.d.ts

@@ -1,2 +1,2 @@
-export * from './Status.schema';
 export * from './Type.schema';
+export * from './Status.schema';