Generating contemporaneous clinical records

Abstract

Presented herein are methods and systems for generating a synchronous clinical record that is reflective of contemporaneous activity pertaining to at least one of operation or management of a medical device. One or more contemporaneous clinical activities of a clinical session are monitored to generate a contemporaneous activity log. An artificial intelligence (AI) model is applied to process the contemporaneous activity log. Based on the processing, the AI model generates a synchronous clinical record that is reflective of the one or more contemporaneous clinical activities.

Description

GENERATING CONTEMPORANEOUS CEINICAE RECORDSBACKGROUNDField of the Invention[oooi] The present invention relates generally to techniques for generating synchronous clinical records reflective of contemporaneous clinical activities pertaining to a clinical session associated with a medical device.Related Art

[0002] Medical devices have provided a wide range of therapeutic benefits to recipients over recent decades. Medical devices can include internal or implantable components / devices, external or wearable components / devices, or combinations thereof (e.g., a device having an external component communicating with an implantable component). Medical devices, such as traditional hearing aids, partially or fully-implantable hearing prostheses (e.g., bone conduction devices, mechanical stimulators, cochlear implants, etc.), pacemakers, defibrillators, functional electrical stimulation devices, and other medical devices have been successful in performing lifesaving and / or lifestyle enhancement functions and / or recipient monitoring for a number of years.

[0003] The types of medical devices and the ranges of functions performed thereby have increased over the years. For example, many medical devices, sometimes referred to as “implantable medical devices,” now often include one or more instruments, apparatus, sensors, processors, controllers or other functional mechanical or electrical components that are permanently or temporarily implanted in a recipient. These functional devices are typically used to diagnose, prevent, monitor, treat, or manage a disease / injury or symptom thereof, or to investigate, replace or modify the anatomy or a physiological process. Many of these functional devices utilize power and / or data received from external devices that are part of, or operate in conjunction with, implantable components.SUMMARY

[0004] In one aspect, a method is provided. The method comprises: monitoring a clinical session during which one or more operational settings of a medical device are configured; and generating, with an artificial intelligence (Al) model, a synchronous clinical record based on the monitoring.

[0005] In another aspect, a second method is provided. The method comprises: obtaining a user prompt from a user; obtaining a contemporaneous activity log captured during a hearing device fitting session; and generating, by an artificial intelligence (Al) model, a clinical summary of the fitting session based on the user prompt and the contemporaneous activity log.

[0006] In another aspect, a third method is provided. The method comprises: obtaining a user prompt from a user; processing, by an artificial intelligence (Al) model, a contemporaneous activity log associated with a clinical session based on the user prompt; and generating, by the Al model, a synchronous clinical record based on the processing.

[0007] In another aspect, one or more non-transitory computer readable storage media are provided. The one or more non-transitory computer readable storage media comprise instructions that, when executed by a processor, cause the processor to: obtain a contemporaneous activity log of a clinical session; and generate, by an artificial intelligence (Al) model, a synchronous clinical record based on the contemporaneous activity log; and configure one or more operational settings of a medical device based on the synchronous clinical record.

[0008] In another aspect, a system is provided. The system comprises: a memory; and at least one processor operable coupled to the memory, wherein the at least one processor is configured to: generate a contemporaneous activity log of one or more clinical activities performed during a clinical session; apply an artificial intelligence (Al) model to generate a synchronous clinical record reflective of the contemporaneous activity log; and update the synchronous clinical record based on feedback from a user.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Embodiments of the present invention are described herein in conjunction with the accompanying drawings, in which:

[0010] FIG. 1A is a flowchart illustrating a method for generating a synchronous clinical record, in accordance with certain embodiments presented herein;

[0011] FIG. IB is a flowchart illustrating another method for generating a synchronous clinical record, in accordance with certain embodiments presented herein;

[0012] FIG. 2 is a flowchart illustrating a method for generating a synchronous clinical record based on a user prompt, in accordance with certain embodiments presented herein;

[0013] FIG. 3 is a flowchart illustrating a method for training an artificial intelligence (Al) model, in accordance with certain embodiments presented herein;

[0014] FIG. 4 is a flowchart illustrating a method, in accordance with certain embodiments presented herein;

[0015] FIG. 5 is a flowchart illustrating another method, in accordance with certain embodiments presented herein;

[0016] FIG. 6 is a flowchart illustrating another method, in accordance with certain embodiments presented herein;

[0017] FIG. 7 is a flowchart illustrating operations performed by a processor executing instructions stored in one or more non-transitory computer readable storage media, in accordance with certain embodiments presented herein;

[0018] FIG. 8 is a flowchart illustrating operations performed by a system comprising a memory and at least one processor operable coupled to the memory, wherein the at least one processor is configured to perform the operations, in accordance with certain embodiments presented herein;

[0019] FIG. 9 is a schematic diagram illustrating a computing device with which aspects of the techniques presented herein can be implemented;

[0020] FIG. 10 is a schematic diagram illustrating a vestibular stimulator system with which aspects of the techniques presented herein can be implemented;

[0021] FIG. 11 is a schematic diagram illustrating a retinal prosthesis system with which aspects of the techniques presented herein can be implemented;

[0022] FIG. 12A is a schematic diagram illustrating a cochlear implant system with which aspects of the techniques presented herein can be implemented;

[0023] FIG. 12B is a side view of a recipient wearing a sound processing unit of the cochlear implant system of FIG. 12A;

[0024] FIG. 12C is a schematic view of components of the cochlear implant system of FIG. 12A; and

[0025] FIG. 12D is a block diagram of the cochlear implant system of FIG. 12A.DETAILED DESCRIPTION

[0026] It is common practice for medical practitioners to participate in clinical sessions in association with a medical device that is worn by, implanted in, etc., a recipient. These clinical sessions could be performed for a variety of reasons, such as to initially “fit” or configure (e.g., program) the medical device for the recipient, to adjust / refine parameters / settings of the medical device, to troubleshoot problems with the medical device, etc. In conventional arrangements, after a clinical session has concluded, the medical practitioner (e.g., clinician) generally prepares (e.g., types, dictates, etc.) a report or record of the clinical activities performed during the clinical session, referred to as a “clinical record.” The clinical record is typically stored in an electronic health records system for subsequent use. For example, after a medical device (e.g., cochlear implant or insulin pump) fitting session, a medical practitioner can generate a clinical record comprising operational settings of the medical device, recipient preferences and feedback, and other relevant clinical information. The medical practitioner can then store or upload the clinical record to an electronic health record system accessible by other medical practitioners, the recipient, etc.

[0027] Accurate and up-to-date clinical records enhance a medical practitioner’s ability to deliver consistent care to recipients, but the conventional processes for preparation of clinical records suffer from a number of drawbacks. For example, depending on the scope of the clinical activity, it can be time-consuming for a medical practitioner to prepare a complete clinical record immediately after a clinical session. As such, it is possible that some clinical records may not be completed until hours or even days after the clinical session. The lack of real-time recordation increases the likelihood of inaccurate description and / or missing information. Therefore, it is important that contemporaneous clinical activities are monitored and recorded in real-time. Further, since conventional clinical records written by variousmedical practitioners can differ in content and style, it may be difficult for another medical practitioner to determine the scope of prior clinical activities. Therefore, it is desirable to streamline the process of contemporaneous clinical record generation to ensure medical practitioners are making decisions based on accurate information.

[0028] In order to address the above and other challenges, presented herein are techniques for automated or semi-automated generation of a synchronous clinical record that is reflective of contemporaneous clinical activity. In certain examples, an artificial intelligence (Al) model is applied to generate the synchronous clinical record.

[0029] More specifically, in accordance with embodiments presented herein, a clinical session (e.g., fitting session) associated with a medical device is monitored to generate a contemporaneous activity log. The contemporaneous activity log is an account of the clinical activities performed during the clinical session (e.g., contemporaneous activity pertaining to the operation or management of the medical device) and related clinical information (e.g., data related to one or more settings of the medical device, recipient feedback, medical practitioner’s notes).

[0030] In accordance with certain embodiments presented herein, an Al model is applied to process the contemporaneous activity log and to generate a synchronous clinical record reflective of contemporaneous activity pertaining to the operation or management of the medical device. In certain embodiments described further below, the synchronous clinical record is generated by the Al model in real-time, thus reducing the likelihood of inaccurate or missing information due to human error. Further, applying the Al model to generate the synchronous clinical record saves time for medical practitioners, thus providing improved efficiency. Moreover, conventional clinical records often contain complex medical language that, while clear to medical practitioners, can be challenging for patients or recipients to understand. Leveraging an Al model to generate synchronous clinical records using simple language that is accessible to patients or recipients can help them better comprehend and track what has occurred during their medical treatment.

[0031] Further, applying an Al model to generate synchronous clinical records in a standardized format can assist medical practitioners adhere to standard protocols during clinical sessions. For example, the Al model can compare the contemporary activity log with established protocols to determine missed steps in a clinical session. The medical practitioner may be notified of the missed steps while reviewing the synchronous clinical record, andimmediately make corrections during the clinical session. Alternatively, the Al model can generate recommendations to include the missed steps for the patient’s next clinical visit. As a result, using Al-generated synchronous clinical records can ensure that when established protocol steps are not followed, it is a clinical choice made based on the medical practitioner’s expertise, and not due to human error. Overall, incorporating Al-generated synchronous clinical records in the clinical experience can enhance medical practitioners’ ability to provide consistent and quality care to patients or recipients.

[0032] In one example, the synchronous clinical record comprises one or more summaries of the contemporaneous activity log. The one or more summaries, generated by the Al model, can follow a standardized format to ensure medical practitioners, recipients, and / or other users (e.g., recipient caregivers) can easily review the clinical activities that have been performed. Further, in another example, the synchronous clinical record comprises one or more recommendations of future clinical activities generated by the Al model based on the contemporaneous activity log.

[0033] In certain embodiments, a user prompt is obtained and used during generation of the synchronous clinical record. For example, through the user prompt, a user can specify that certain types of information pertaining to the operation or management of the medical device should be included in the one or more summaries generated by the Al model. In some examples, the user can further modify the user prompt after reviewing the one or more summaries generated by the Al model. The one or more summaries can be further adjusted based on the modified user prompt. As a result, aspects of the techniques presented herein allow a user (e.g., a medical practitioner) to review and update the one or more summaries generated by the Al model to ensure the synchronous clinical record accurately reflects the clinical activities that have been performed.

[0034] In certain embodiments, as described further below, the Al model can be a machine learning (ML) model, generative Al model (e.g., generative adversarial network), large language model (LLM), transformer model, reinforcement learning model, neural network model (e.g., convolutional neural network, recurrent neural network), ensemble or mixture of a plurality of Al models, or any Al model suitable to process an activity log. In certain embodiments, the Al model can be a custom Al model that is tailored to perform a specific task, such as generating synchronous clinical records reflective of contemporaneous clinical activities. In other embodiments, the Al model can be trained to perform a general or specifictask and applied in the embodiments described herein through an application programming interface (API) call.

[0035] FIG. 1A is a flowchart illustrating a method 100A, in accordance with certain embodiments presented herein. Method 100A begins at 103 where a clinical session is monitored to generate a contemporaneous activity log. Then, at 105, the contemporaneous activity log is processed with an Al model. Based on the processing at 105, the Al model generates a synchronous clinical record that is reflective of contemporaneous activity pertaining to the medical device at 107. Once the synchronous clinical record is generated, the method 100A outputs the synchronous clinical record to one or more users at 109. Then, in certain embodiments, the method 100A proceeds to input the synchronous clinical record into a documentation system / application at 113 and / or transmit the synchronous clinical record to a computer application at 115. Alternatively, in certain embodiments, the method 100A proceeds to 113 and / or 115 directly after the synchronous clinical record is generated by the Al model at 107.

[0036] In operation, at 103, one or more contemporaneous clinical activities performed during a clinical session are monitored, during which one or more operational settings of a medical device are determined / configured. In certain embodiments, a clinical software application (e.g., medical device fitting software application) can generate the contemporaneous activity log in real-time during or immediately after the clinical session. In certain examples, the contemporaneous activity log can be stored in an electronic database, a cloud database, or any suitable medium that is able to store one or more data records.

[0037] In certain embodiments, the contemporaneous activity log comprises an account of clinical activities performed during a clinical session and related clinical information. More specifically, the contemporaneous activity log can include an account of contemporaneous activity pertaining to the operation or management of the medical device in the clinical session (e.g., medical device fitting session). For example, the contemporaneous activity log can comprise data related to the operational settings of the medical device (e.g., one or mor operational settings of the medical device at the beginning of the clinical session, one or more operational settings of the medical device at the end of the clinical session, data related to changes / adjustments made to one or more operational settings of the medical device during the clinical session, etc.) or description of tests performed during the clinical session. Further, the contemporaneous activity log can include clinical information related to the clinical session. For example, the contemporaneous activity log can include one or more results of testsperformed during the fitting session, recipient preferences and feedback, medical practitioner’s notes, the recipient’s medical history, data related to the performance and / or configuration of the medical device, description of remote monitoring capabilities associated with the medical device, or any other data affiliated with the clinical session.

[0038] The contemporaneous activity log can include numerical values, textual descriptions, images, sound recordings, and / or a combination thereof. In certain embodiments, the contemporaneous activity log can include one or more operational settings of the medical device automatically logged by the clinical software application, data provided by the medical practitioner and / or recipient, data obtained from an external source, and / or a combination thereof.

[0039] In certain embodiments, a medical practitioner can input observations of recipient preferences or feedback into the clinical software application through a user interface. In one example, a medical practitioner can input text description of the recipient’s preferences on volume control into the clinical software application through a text input box. In another example, a medical practitioner can check a box on the user interface of the clinical software application to indicate the recipient is satisfied with the fitting of the medical device.

[0040] In certain embodiments, a contemporaneous activity log is generated from monitoring a cochlear implant fitting session. In these embodiments, for example, the contemporaneous activity log comprises descriptions of a medical practitioner (e.g., clinician) adjusting one or more operational settings of the cochlear implant (e.g., adjusting threshold level and / or comfort level). Table 1, below, provides a list of example categories and descriptions of data that can be recorded in the contemporaneous activity log generated from monitoring a cochlear implant fitting session.Table 1- Categories and Descriptions of Contemporaneous Activities Monitored in a CochlearImplant Fitting Session

[0041] In certain embodiments, a contemporaneous activity log is generated from monitoring a hearing aid fitting session. In these embodiments, for example, the contemporaneous activity log comprises descriptions of adjustments to gain settings performed during the fitting session. Table 2, below, provides a list of example categories and descriptions of data that can be recorded in the contemporaneous activity log generated from monitoring a hearing aid fitting session.Table 2- Categories and Descriptions of Contemporaneous Activities Monitored in a HearingAid Fitting Session

[0042] In certain embodiments, a contemporaneous activity log is generated from monitoring an insulin pump calibration session. In these embodiments, for example, the contemporaneous activity log comprises descriptions of sensor integration or alarm history. Table 3, below, provides a list of example categories and descriptions of data that can be recorded in the contemporaneous activity log generated from monitoring an insulin pump calibration session.Table 3- Categories and Descriptions of Contemporaneous Activities Monitored in an Insulin Pump Calibration Session

[0043] As noted above, the contemporaneous activity log generated at 103 is processed with an Al model at 105. In certain embodiments, the contemporaneous activity log can include raw data that is preprocessed prior to being input to the Al model. In these embodiments, the contemporaneous activity log is converted to a data format that can be processed by the Al model using one or more data preprocessing techniques. In one example, data preprocessing techniques such as vectorization can be applied to transform the contemporaneous activity log into one or more vectors representing data in the contemporaneous activity log. By way of example, data preprocessing techniques that can be applied include data normalization, feature extraction, dimensionality reduction, or any technique that converts raw data to a data format that can be processed by an Al model.

[0044] At 107, the Al model generates a synchronous clinical record based on the processing performed at 105. In certain embodiments, the synchronous clinical record is reflective of contemporaneous activity pertaining to at least one of operation or management of the medical device. More specifically, in certain embodiments, the synchronous clinical record generated by the Al model can include one or more summaries of contemporary clinical activities and / or one or more recommendations of future clinical activities. In certain embodiments, the one or more summaries and / or recommendations generated by the Al model can be expressed in natural language and follow a standardized format (e.g., predetermined template) to ensure the synchronous clinical record is consistent and easy to understand.

[0045] In certain embodiments, the synchronous clinical record can be utilized by a medical practitioner to instantiate and / or configure the one or more operational settings of the medical device in a clinical session. In one example, the one or more summaries of a cochlear implantfiting session generated by the Al model can indicate the type of test performed (e.g., monosyllabic word recognition), adjustments made to one or more operational setings of the medical device (e.g., threshold level and / or comfort level), or any other information pertaining to the fiting session (e.g., categories of information described in Table 1). A medical practitioner can further configure the one or more operational setings of the cochlear implant based on the information in the synchronous clinical record.

[0046] In another example, based on the contemporaneous activity log indicating that a recipient expresses overall satisfaction with current operational setings of the medical device (e.g., cochlear implant) for a specific program (e.g., “everyday” environment), the Al model can generate a recommendation to a medical practitioner to add another program (e.g., an “outdoor” environment) in the recipient’s next fiting session. Based on the recommendation generated by the Al model, the medical practitioner can adjust the one or more setings of the medical device in accordance with the “outdoor” program in the next fiting session.

[0047] After the synchronous clinical record is generated at 107, the method 100A outputs the synchronous clinical record to one or more users at 109. In certain embodiments, prior to outputing the synchronous clinical record at 109, the synchronous clinical record generated at 107 can be further modified by the Al model to fit the needs of a specific user. In one example, the synchronous clinical record can be modified such that it uses language that is accessible to a recipient (e.g., avoid medical jargons). In another example, the synchronous clinical record can be modified to include additional medical language or details if the synchronous clinical record is intended for output to a medical practitioner.

[0048] In certain embodiments, the synchronous clinical record can be displayed on a graphical user interface of a computing device, such as a personal computer (e.g., laptop, desktop, tablet) or a mobile phone (e.g., smartphone). In one example, the synchronous clinical record can be displayed in real-time to the one or more users while the clinical session is ongoing, thus allowing the user to track a recipient’s clinical experience. In another example, the synchronous clinical record can be generated in real-time and then displayed to the one or more users after the clinical session has concluded. In certain embodiments, the one or more users can be a medical practitioner, a recipient, and / or any individual permited to have access to the synchronous clinical record.

[0049] In certain embodiments, after the synchronous clinical record is output to the one or more users at 109, the method 100A proceeds to input the synchronous clinical record into adocumentation system / application at 113 and / or transmit the synchronous clinical record to a computer application at 115. Alternatively, in certain embodiments, the method 100A proceeds to 113 and / or 115 directly after the synchronous clinical record is generated by the Al model at 107.

[0050] In certain embodiments, the one or more users can review and input the synchronous clinical record into a documentation system / application at 113. For example, the one or more users (e.g. medical practitioner) can copy the text of the synchronous clinical record generated by the Al model and input the text into the documentation system / application to document the clinical activities performed during the clinical session. Alternatively, in certain embodiments, the synchronous clinical record generated at 107 is automatically input to the documentation system / application at 113.

[0051] In certain embodiments, the documentation system / application can be a computer application, a mobile application, a database, or any suitable system / application for inputting clinical records. By way of example, the documentation system / application can be a clinical activity documentation system / application or an electronic health records system / application. In certain examples, the documentation system / application can allow the one or more users to input the synchronous clinical record as a journal entry. In other examples, the documentation system / application automatically creates a journal entry for the synchronous clinical record.

[0052] Additionally or alternatively, the method 100A transmits the synchronous clinical record obtained at 107 and / or 109 to a computer application (e.g. electronic health records software application) at 115. For example, the synchronous clinical record can be transmited to the electronic health records software application through an API. In this example, the one or more users (e.g. medical practitioner or recipient) can view the synchronous clinical record in the electronic health records software application after the synchronous clinical record is exported to the electronic health records software application. In certain embodiments, the electronic health records software application can be a computer or mobile application.

[0053] In certain embodiments, the generation of a synchronous clinical record by an Al model in method 100A can be automated or semi-automated. In one example, the generation of a synchronous clinical record by the Al model is automated. In this example, the contemporaneous activity log generated at 103 includes one or more operational settings of the medical device that are automatically logged by a clinical software application. Then, the Al model automatically processes the contemporaneous activity log at 105 and generates asynchronous clinical record at 107. In another example, the generation of a synchronous clinical record by the Al model is semi-automated. That is, for example, the contemporaneous activity log generated at 103 includes a combination of data automatically logged by a clinical software application (e.g., one or more operational settings of the medical device) and data manually provided by a user (e.g., description of recipient preference). Then, the Al model processes the contemporaneous activity log at 105 and generates a synchronous clinical record at 107.

[0054] FIG. IB is a flow chart illustrating further details of the method 100B, in accordance with certain embodiments presented herein. Method 100B begins at 103 where a clinical session is monitored to generate a contemporaneous activity log. Then, at 105, the contemporaneous activity log is processed with an Al model. Based on the processing at 105, the Al model generates a synchronous clinical record that is reflective of contemporaneous activity pertaining to the medical device at 107. Once the synchronous clinical record is generated, the method 100B outputs the synchronous clinical record to one or more users at 109. Then, in certain embodiments, the method 100B proceeds to input the synchronous clinical record into a documentation system / application at 113 and / or transmit the synchronous clinical record to a computer application at 115.

[0055] After the synchronous clinical record is output to the one or more users at 109, the method 100B proceeds to 117 where feedback is received from the one or more users in relation to the synchronous clinical record generated by the Al model. That is, for example, the user can indicate that the synchronous clinical record contains inaccurate summaries of clinical activities or is missing certain information. At 119, the Al model is applied to update the synchronous clinical record based on the one or more users’ feedback. Then, the method 100B returns to 109, where the updated synchronous clinical record is output to the one or more users. Here, the method 100B proceeds iteratively to apply the Al model to update the synchronous clinical record based on user feedback. As such, the synchronous clinical record is refined to accurately reflect the contemporaneous clinical activities. In certain embodiments, when a user is satisfied with the accuracy of the synchronous clinical record (e.g., the user does not provide feedback), the method 100B proceeds to input the synchronous clinical record into a documentation system / application at 113 and / or transmit the synchronous clinical record to a computer application at 115.

[0056] FIG. 2 is a flowchart illustrating a method 200, in accordance with certain embodiments presented herein. Method 200 begins at 201 where a user prompt is obtained from a user (e.g.,medical practitioner). In certain embodiments, the user prompt can be a text input, expressed in natural language, that indicates specific types of information that the user would like included in a synchronous clinical record. In one example, the user prompt can be obtained through a graphical user interface of a computing device.

[0057] At 203, a clinical session is monitored to generate a contemporaneous activity log. In certain embodiments, data preprocessing techniques such as vectorization can be applied to transform the contemporaneous activity log in the form of raw data into one or more vectors that can be processed by an Al model. By way of example, data preprocessing techniques that can be applied include data normalization, feature extraction, dimensionality reduction, or any technique that converts raw data to a data format that can be processed by an Al model.

[0058] Then, at 205, the contemporaneous activity log is processed with an Al model. In operation, the Al model processes the contemporaneous activity log based on the user prompt obtained at 201. For example, the Al model can parse the user prompt to identify a user intent and process the contemporaneous activity log based on the user intent. Then, at 207, the Al model generates a synchronous clinical record that is reflective of the user intent expressed in the user prompt. As noted above, in certain embodiments, the synchronous clinical record comprises one or more summaries of the contemporaneous activity log and / or one or more recommendations of future clinical activities generated by the Al model.

[0059] By way of example, a user (e.g., medical practitioner) can provide a user prompt indicating that a synchronous clinical record for a particular device (e.g., cochlear implant) fitting session should reflect several categories of information. For example, the user can input “add information regarding whether feedback management was performed, type of program, and noise cancellation settings.” The Al model can parse the user prompt to identify the categories of information that must be included in the synchronous clinical record. Then, based on the user prompt, the Al model processes the contemporary activity log to generate a synchronous clinical record that includes the following example text in the form of a summary, “feedback measurement performed; initial “Everyday” program configured; and noise cancelling set to strong.”

[0060] At 209, the synchronous clinical record generated at 207 is output to one or more users. Then, at 221, the synchronous clinical record is reviewed by the one or more users (e.g., medical practitioner) and an indication can be obtained from the one or more users that the synchronous clinical record needs to be modified. In operation, the indication can be obtainedin the form of another user prompt provided by a user. For example, through another user prompt, the user can indicate a desire to update the synchronous clinical record (e.g., “add information that the user expresses overall satisfaction” or “add an outdoor program next time”). In certain embodiments where the synchronous clinical record is displayed in an interface (e.g., graphical user interface), the interface can include an interactive element (e.g., a button labeled “modify”) that would allow the user to indicate a desire to modify the synchronous clinical record. In this example, the user can input a user prompt and click on the “modify” button to indicate that the synchronous clinical record is to be modified based on the user prompt.

[0061] If the one or more users indicate that the synchronous clinical record is to be modified at 221, the user prompt is modified at 223. Then, the method 200 returns to 205, where the contemporaneous activity log is processed with the Al model based on a user prompt (including a modified user prompt). In operation, the Al model processes the contemporaneous activity log based on the modified user prompt obtained at 223. For example, the Al model can parse the modified user prompt to identify a user intent and process the contemporaneous activity log based on the user intent. By way of example, if the user provides the modified user prompt “add information that the user expresses overall satisfaction” after reviewing the synchronous clinical record generated by the Al model, the Al model can update the synchronous clinical record to include that “the user expresses overall satisfaction with the current settings.” The method 200 proceeds iteratively if the user continues to indicate a desire to modify the synchronous clinical record at 221. Allowing the user to review and update the synchronous clinical record through a modified user prompt ensures the synchronous clinical record is dynamically updated to reflect the most accurate and up-to-date information.

[0062] If at 221 the one or more users do not indicate that the synchronous clinical record needs to be modified, the one or more users can review and input the synchronous clinical record into a documentation system / application at 225. For example, the one or more users (e.g. medical practitioner) can copy the text of the synchronous clinical record generated by the Al model and input the text into the documentation system / application to document the clinical activities performed during the clinical session. In certain embodiments, the documentation system / application can be a computer application, a mobile application, a database, or any suitable system / application for inputting clinical records. By way of example, the documentation system / application can be a clinical activity documentation system / application or an electronic health records system / application. In certain examples, thedocumentation system / application can allow the one or more users to input the synchronous clinical record as a journal entry.

[0063] Additionally or alternatively, the method 200 transmits the synchronous clinical record to a computer application (e.g. electronic health records software application) at 227. For example, the synchronous clinical record can be transmitted to the electronic health records software application through an API. In this example, the one or more users (e.g. medical practitioner or recipient) can view the synchronous clinical record in the electronic health records software application after the synchronous clinical record is exported to the electronic health records software application. In certain embodiments, the electronic health records software application can be a computer or mobile application.

[0064] FIG. 3 is a flowchart illustrating a method 300, in accordance with certain embodiments presented herein. Method 300 describes details of training an Al model that can be applied in certain embodiments presented herein. At 351, training data is obtained from a plurality of historical activity logs. In operation, the training data can be extracted from the plurality of historical activity logs associated with historical clinical sessions during which clinical activities were performed. More specifically, each of the plurality of historical activity logs comprises descriptions of one or more clinical activities pertaining to at least one of operation or management of a medical device monitored in a clinical session. For example, a historical activity log can comprise one or more operational settings of a medical device, one or more results of tests performed, recipient preferences, medical practitioner’s notes, etc. Tables 1, 2, and 3 described above provide example categories of data that can be included in activity logs of clinical sessions in certain embodiments presented herein.

[0065] Further, in certain embodiments, the training data can include both the plurality of historical activity logs and corresponding synchronous clinical records. In these embodiments, the training data includes a plurality of pairs of data, wherein each pair comprises a historical activity log and a corresponding synchronous clinical record that reflects the activities and / or information described in the historical activity log. The corresponding synchronous clinical record can be prepared by a human (e.g., medical practitioner) or generated by a computer and / or machine. In certain embodiments, the training data can be labeled training data. For example, each pair of historical activity log and corresponding synchronous clinical record has a corresponding label indicating whether the synchronous clinical record accurately reflects the activities and / or information described in the historical activity log. For example, the label can be categorical (e.g., accurate or inaccurate). In certain embodiments, the label can be assignedby a human annotator, such as a clinical subject matter expert, after the human annotator reviews a historical activity log and its corresponding synchronous clinical record.

[0066] At 353, the training data obtained at 351 is used as input to train an Al model using any technique suitable for training the Al model. Once the Al model is trained at 353, the method 300 proceeds to evaluate a performance metric (e.g., accuracy) of the Al model. At 355, if the performance metric of the Al model does not meet a threshold, the method 300 returns to 353 to iteratively train the model. However, if the performance metric of the Al model meets the threshold, the Al model is deemed to have been sufficiently trained. At this point, the Al model is applied to generate a synchronous clinical record at 357.

[0067] FIG. 4 is a flowchart illustrating a method 400, in accordance with certain embodiments presented herein. Method 400 begins at 461 where a clinical session during which one or more operational settings of a medical device are configured is monitored. For example, one or more contemporaneous activities of the clinical session are monitored. Then, at 462, an Al model generates a synchronous clinical record based on the monitoring.

[0068] FIG. 5 is a flowchart illustrating a method 500, in accordance with certain embodiments presented herein. Method 500 begins at 567 where a user prompt is obtained from a user. At 568, a contemporaneous activity log captured during a hearing device fitting session is obtained. For example, the contemporaneous activity log is obtained by monitoring a hearing device fitting session during which one or more operational settings of the hearing device are determined. Then, at 569, a clinical summary of the fitting session is generated by an Al model based on the user prompt and the contemporaneous activity log.

[0069] FIG. 6 is a flowchart illustrating a method 600, in accordance with certain embodiments presented herein. Method 600 begins at 671 where a user prompt is obtained from a user. Then, at 672, an Al model processes a contemporaneous activity log associated with a clinical session based on the user prompt. At 673, the Al model generates a synchronous clinical record based on the processing. For example, the synchronous clinical record comprises one or more clinical summaries or one or more recommendations.

[0070] FIG. 7 is a flowchart illustrating operations performed by a processor executing instructions stored in one or more non-transitory computer readable storage media, in accordance with certain embodiments presented herein. At 776, a contemporaneous activity log of a clinical session is obtained. At 777, an Al model generates a synchronous clinical record based on the contemporaneous activity log. For example, the synchronous clinical record comprises one or more clinical summaries or one or more recommendations. Then, at 778, one or more operational settings of a medical device are configured based on the synchronous clinical record.

[0071] FIG. 8 is a flowchart illustrating operations performed by a system comprising a memory and at least one processor operable coupled to the memory, wherein the at least one processor is configured to perform the operations, in accordance with certain embodiments presented herein. At 881, a contemporaneous activity log of one or more clinical activities performed during a clinical session is generated. For example, the contemporaneous activity log comprises descriptions of one or more activities pertaining to a medical device monitored in the clinical session. Then, at 882, an Al model is applied to generate a synchronous clinical record that is reflective of the contemporaneous activity log. At 883, the synchronous clinical record is updated based on feedback from a user.

[0072] FIG. 9 is a block diagram illustrating one example arrangement for a computing device 910 configured to perform one or more operations in accordance with certain embodiments presented herein. As shown in FIG. 9, in its most basic configuration, the computing device 910 includes at least one processing unit 983 and a memory 984. The processing unit 983 includes one or more hardware or software processors (e.g., Central Processing Units) that can obtain and execute instructions. The processing unit 983 can communicate with and control the performance of other components of the computing device 910. The memory 984 is one or more software or hardware-based computer-readable storage media operable to store information accessible by the processing unit 983. The memory 984 can store, among other things, instructions executable by the processing unit 983 to implement applications or cause performance of operations described herein, as well as other data. The memory 984 can be volatile memory (e.g., RAM), non-volatile memory (e.g., ROM), or combinations thereof. The memory 984 can include transitory memory or non-transitory memory. The memory 984 can also include one or more removable or non-removable storage devices. In examples, the memory 984 can include RAM, ROM) EEPROM (Electronically-Erasable Programmable Read-Only Memory), flash memory, optical disc storage, magnetic storage, solid state storage,or any other memory media usable to store information for later access. By way of example, and not limitation, the memory 984 can include wired media, such as a wired network or direct- wired connection, and wireless media, such as acoustic, RF, infrared, other wireless media, or combinations thereof. In certain embodiments, the memory 984 comprises logic 995 that, when executed, enables the processing unit 983 to perform aspects of the techniques presented (e.g., the operations of FIGs. 1A, IB, 2, 3, 4, 5, 6, 7, or 8).

[0073] In the illustrated example of FIG. 9, the computing device 910 further includes a network adapter 986, one or more input devices 987, and one or more output devices 988. The computing device 910 can include other components, such as a system bus, component interfaces, a graphics system, a power source (e.g., a battery), among other components. The network adapter 986 is a component of the computing device 910 that provides network access (e.g., access to at least one network 989). The network adapter 986 can provide wired or wireless network access and can support one or more of a variety of communication technologies and protocols, such as Ethernet, cellular, Bluetooth, near-field communication, and RF, among others. The network adapter 986 can include one or more antennas and associated components configured for wireless communication according to one or more wireless communication technologies and protocols. The one or more input devices 987 are devices over which the computing device 910 receives input from a user. The one or more input devices 987 can include physically-actuatable user-interface elements (e.g., buttons, switches, or dials), a keypad, keyboard, mouse, touchscreen, and voice input devices, among other input devices that can accept user input. The one or more output devices 988 are devices by which the computing device 910 is able to provide output to a user. The output devices 988 can include a display 990 (e.g., a liquid crystal display (LCD)) and one or more speakers 991, among other output devices for presentation of visual or audible information to the recipient, a medical practitioner (e.g., clinician or audiologist), or another user.

[0074] It is to be appreciated that the arrangement for the computing device 910 shown in FIG. 9 is merely illustrative and that aspects of the techniques presented herein can be implemented at a number of different types of systems / devices including any combination of hardware, software, and / or firmware configured to perform the functions described herein. For example, the computing device 910 can be a personal computer (e.g., a desktop or laptop computer), a hand-held device (e.g., a tablet computer), a mobile device (e.g., a smartphone), a surgical system, and / or any other electronic device having the capabilities to perform the associated operations described elsewhere herein.

[0075] In certain embodiments, the techniques presented herein can be leveraged for use in generating a synchronous clinical record that is reflective of contemporaneous clinical activity. More specifically, a clinical session (e.g., fitting session) of a medical device is monitored to generate a contemporaneous activity log. Then, an Al model processes the contemporaneous activity log to generate a synchronous clinical record reflective of contemporaneous activity pertaining to an operation or management of the medical device.

[0076] In certain embodiments, the synchronous clinical record generated by the Al model comprises one or more summaries of clinical activities performed in a clinical session and / or one or more recommendations of future clinical activities. Based on the synchronous clinical record, a medical practitioner can instantiate and / or configure one or more settings of the medical device to prepare for a recipient’s clinical session.

[0077] In certain embodiments, a user, through a user prompt, can specify that certain types of information pertaining to the operation or management of the medical device should be included in the synchronous clinical record. The user can further modify the user prompt after reviewing the synchronous clinical record generated by the Al model. Based on the modified user prompt, the Al model can update the synchronous clinical record.

[0078] There are a number of different types of devices in / with which embodiments of the present invention can be implemented. Merely for ease of description, the techniques presented herein are primarily described with reference to a specific device in the form of a cochlear implant system. However, it is to be appreciated that the techniques presented herein can also be partially or fully implemented by any of a number of different types of devices, including consumer electronic device (e.g., mobile phones), wearable devices (e.g., smartwatches), hearing devices, implantable medical devices, consumer electronic devices, etc. As used herein, the term “hearing device” is to be broadly construed as any device that acts on an acoustical perception of an individual, including to improve perception of sound signals, to reduce perception of sound signals, etc. In particular, a hearing device can deliver sound signals to a user in any form, including in the form of acoustical stimulation, mechanical stimulation, electrical stimulation, etc., and / or can operate to suppress all or some sound signals. As such, a hearing device can be a device for use by a hearing-impaired person (e.g., hearing aids, middle ear auditory prostheses, bone conduction devices, direct acoustic stimulators, electro-acoustic hearing prostheses, auditory brainstem stimulators, bimodal hearing prostheses, bilateral hearing prostheses, dedicated tinnitus therapy devices, tinnitus therapy device systems, combinations or variations thereof, etc.), a device for use by a personwith normal hearing (e.g., consumer devices that provide audio streaming, consumer headphones, earphones, and other listening devices), a hearing protection device, etc. In other examples, the techniques presented herein can be implemented by, or used in conjunction with, various implantable medical devices, such as visual devices (i.e., bionic eyes), sensors, pacemakers, drug delivery systems, defibrillators, functional electrical stimulation devices, catheters, seizure devices (e.g., devices for monitoring and / or treating epileptic events), sleep apnea devices, electroporation devices, etc.

[0079] . Example devices that can benefit from technology disclosed herein are described in more detail in FIGS. 10, 11, and 12A-12D. For example, FIG. 10 illustrates an example vestibular stimulator system 1002, with which embodiments presented herein can be implemented. As shown, the vestibular stimulator system 1002 comprises an implantable component (vestibular stimulator) 1012 and an external device / component 1004 (e.g., external processing device, battery charger, remote control, etc.). The external device 1004 comprises a transceiver unit 1060. As such, the external device 1004 is configured to transfer data (and potentially power) to the vestibular stimulator 1012.

[0080] The vestibular stimulator 1012 comprises an implant body (main module) 1034, a lead region 1036, and a stimulating assembly 1016, all configured to be implanted under the skin / tissue (tissue) 1015 of the recipient. The implant body 1034 generally comprises a hermetically-sealed housing 1038 in which RF interface circuitry, one or more rechargeable batteries, one or more processors, and a stimulator unit are disposed. The implant body 1234 also includes an intemal / implantable coil 1014 that is generally external to the housing 1038, but which is connected to the transceiver via a hermetic feedthrough (not shown).

[0081] The stimulating assembly 1016 comprises a plurality of electrodes 1044( l)-(3) disposed in a carrier member (e.g., a flexible silicone body). In this specific example, the stimulating assembly 1016 comprises three (3) stimulation electrodes, referred to as stimulation electrodes 1044(1), 1044(2), and 1044(3). The stimulation electrodes 1044(1), 1044(2), and 1044(3) function as an electrical interface for delivery of electrical stimulation signals to the recipient’s vestibular system.

[0082] The stimulating assembly 1016 is configured such that a surgeon can implant the stimulating assembly adjacent the recipient’s otolith organs via, for example, the recipient’s oval window. It is to be appreciated that this specific embodiment with three stimulation electrodes is merely illustrative and that the techniques presented herein can be used withstimulating assemblies having different numbers of stimulation electrodes, stimulating assemblies having different lengths, etc.

[0083] In operation, the vestibular stimulator 1012, the external device 1004, and / or another external device can be configured to implement the techniques presented herein. That is, the vestibular stimulator 1012, possibly in combination with the external device 1004 and / or another external device, can include an evoked biological response analysis system, as described elsewhere herein.

[0084] FIG. 11 illustrates a retinal prosthesis system 1101 that comprises an external device 1110 (which can be a wearable device) configured to communicate with an implantable retinal prosthesis 1100 via signals 1151. The retinal prosthesis 1100 comprises an implanted processing module 1125, and a retinal prosthesis sensor-stimulator 1190 is positioned proximate the retina of a recipient. The external device 1110 and the processing module 1125 can communicate via coils 1108, 1114.

[0085] In an example, sensory inputs (e.g., photons entering the eye) are absorbed by a microelectronic array of the sensor-stimulator 1190 that is hybridized to a glass piece 1192 including, for example, an embedded array of microwires. The glass can have a curved surface that conforms to the inner radius of the retina. The sensor-stimulator 1190 can include a microelectronic imaging device that can be made of thin silicon containing integrated circuitry that convert the incident photons to an electronic charge.

[0086] The processing module 1125 includes an image processor 1123 that is in signal communication with the sensor-stimulator 1190 via, for example, a lead 1188 that extends through surgical incision 1189 formed in the eye wall. In other examples, processing module 1125 is in wireless communication with the sensor-stimulator 1190. The image processor 1123 processes the input into the sensor-stimulator 1190 and provides control signals back to the sensor-stimulator 1190 so the device can provide an output to the optic nerve. That said, in an alternate example, the processing is executed by a component proximate to, or integrated with, the sensor-stimulator 1190. The electric charge resulting from the conversion of the incident photons is converted to a proportional amount of electronic current which is input to a nearby retinal cell layer. The cells fire and a signal is sent to the optic nerve, thus inducing a sight perception.

[0087] The processing module 1125 can be implanted in the recipient and function by communicating with the external device 1110, such as a BTE unit, a pair of eyeglasses, etc.The external device 1110 can include an external light / image capture device (e.g., located in / on a behind-the-ear device or a pair of glasses, etc.), while, as noted above, in some examples, the sensor-stimulator 1190 captures light / images, in which sensor-stimulator 1190 is implanted in the recipient.

[0088] FIGs. 12A-12D illustrate an example cochlear implant system 1202 with which aspects of the techniques presented herein can be implemented. The cochlear implant system 1202 comprises an external component 1204 that is configured to be directly or indirectly attached to the body of the user, and an intemal / implantable component 1212 that is configured to be implanted in or worn on the head of the user. In the examples of FIGs. 12A-12D, the implantable component 1212 is sometimes referred to as a “cochlear implant.” FIG. 12A illustrates the cochlear implant 1212 implanted in the head 1254 of a user, while FIG. 12B is a schematic drawing of the external component 1204 worn on the head 1254 of the user. FIG. 12C is another schematic view of the cochlear implant system 1202, while FIG. 12D illustrates further details of the cochlear implant system 1202. For ease of description, FIGs. 12A-12D will generally be described together.

[0089] In the examples of FIGs. 12A-12D, the external component 1204 comprises a sound processing unit 1206, an external coil 1208, and generally, a magnet fixed relative to the external coil 1208. The cochlear implant 1212 includes an implantable coil 1214, an implant body 1234, and an elongate stimulating assembly 1216 configured to be implanted in the user’s cochlea. In one example, the sound processing unit 1206 is an off-the-ear (OTE) sound processing unit, sometimes referred to herein as an OTE component, that is configured to send data and power to the implantable component 1212. In general, an OTE sound processing unit is a component having a generally cylindrically shaped housing 1211 and which is configured to be magnetically coupled to the user’s head 1254 (e.g., includes an integrated external magnet 1250 configured to be magnetically coupled to an intemal / implantable magnet 1252 in the implantable component 1212). The OTE sound processing unit 1206 also includes an integrated external (headpiece) coil 1208 (the external coil 1208) that is configured to be inductively coupled to the implantable coil 1214.

[0090] It is to be appreciated that the OTE sound processing unit 1206 is merely illustrative of the external devices that could operate with implantable component 1212. For example, in alternative examples, the external component 1204 can comprise a behind-the-ear (BTE) sound processing unit configured to be attached to, and worn adjacent to, the recipient’s ear. A BTE sound processing unit comprises a housing that is shaped to be worn on the outer ear of theuser. In certain examples, the BTE is connected to a separate external coil assembly via a cable, where the external coil assembly is configured to be magnetically and inductively coupled to the implantable coil 1214, while in other embodiments the BTE includes a coil disposed in or on the housing worn on the outer ear of the user. It is also to be appreciated that alternative external components could be located in the user’s ear canal, worn on the body, etc.

[0091] Although the cochlear implant system 1202 includes the sound processing unit 1206 and the cochlear implant 1212, as described below, the cochlear implant 1212 can operate independently from the sound processing unit 1206, for at least a period, to stimulate the user. For example, the cochlear implant 1212 can operate in a first general mode, sometimes referred to as an “external hearing mode,” in which the sound processing unit 1206 captures sound signals which are then used as the basis for delivering stimulation signals to the user. The cochlear implant 1212 can also operate in a second general mode, sometimes referred as an “invisible hearing” mode, in which the sound processing unit 1206 is unable to provide sound signals to the cochlear implant 1212 (e.g., the sound processing unit 1206 is not present, the sound processing unit 1206 is powered-off, the sound processing unit 1206 is malfunctioning, etc.). As such, in the invisible hearing mode, the cochlear implant 1212 captures sound signals itself via implantable sound sensors and then uses those sound signals as the basis for delivering stimulation signals to the user. Further details regarding operation of the cochlear implant 1212 in the external hearing mode are provided below, followed by details regarding operation of the cochlear implant 1212 in the invisible hearing mode. It is to be appreciated that reference to the external hearing mode and the invisible hearing mode is merely illustrative and that the cochlear implant 1212 could also operate in alternative modes.

[0092] In FIGs. 12A and 12C, the cochlear implant system 1202 is shown with an external device 1210, configured to implement aspects of the techniques presented. The external device 1210 is a computing device, such as a personal computer (e.g., laptop, desktop, tablet), a mobile phone (e.g., smartphone), a remote control unit, etc. The external device 1210 and the cochlear implant system 1202 (e.g., sound processing unit 1206 or the cochlear implant 1212) wirelessly communicate via a bi-directional communication link 1226. The bi-directional communication link 1226 can comprise, for example, a short-range communication, such as Bluetooth link, Bluetooth Low Energy (BLE) link, a proprietary link, etc.

[0093] Returning to the example of FIGs. 12A-12D, the sound processing unit 1206 of the external component 1204 also comprises one or more input devices configured to capture and / or receive input signals (e.g., sound or data signals) at the sound processing unit 1206. Theone or more input devices include, for example, one or more sound input devices 1218 (e.g., one or more external microphones, audio input ports, telecoils, etc.), one or more auxiliary input devices 1228 (e.g., audio ports, such as a Direct Audio Input (DAI), data ports, such as a Universal Serial Bus (USB) port, cable port, etc.), and a short-range wireless transmitter / receiver (wireless transceiver) 120 (e.g., for communication with the external device 1210), each located in, on or near the sound processing unit 1206. However, it is to be appreciated that one or more input devices can include additional types of input devices and / or less input devices (e.g., the short-range wireless transceiver 1220 and / or one or more auxiliary input devices 1228 could be omitted).

[0094] The sound processing unit 1206 also comprises the external coil 1208, a charging coil 1230, a closely-coupled radio frequency transmitter / receiver (RF transceiver) 1222, at least one rechargeable battery 1232, and an external sound processing module 1224. The external sound processing module 1224 can be configured to perform a number of operations that are represented in FIG. 12D by a sound processor 1233. The sound processor 1233 can be formed by one or more processors (e.g., one or more Digital Signal Processors (DSPs), one or more uC cores, etc.), firmware, software, etc. arranged to perform operations described herein. That is, the sound processor 1233 can each be implemented as firmware elements, partially or fully implemented with digital logic gates in one or more application-specific integrated circuits (ASICs), partially or fully in software, etc. Although FIG. 12D illustrates the sound processor 1233 as being implemented / performed at the external sound processing module 1224, it is to be appreciated that these elements (e.g., functional operations) could also or alternatively be implemented / performed as part of the implantable sound processing module 1258, as part of the external device 1210, etc.

[0095] Returning to the example of FIGs. 12A-12D, the implantable component 1212 comprises an implant body (main module) 1234, a lead region 1236, and the stimulating assembly 1216, all configured to be implanted under the skin (tissue) 1215 of the user. The implant body 1234 generally comprises a hermetically-sealed housing 1238 that includes, in certain examples, at least one power source 1225 (e.g., one or more batteries, one or more capacitors, etc.), in which the RF interface circuitry 1240 and a stimulator unit 1242 are disposed. The implant body 1234 also includes the intemal / implantable coil 1214 that is generally external to the housing 1238, but which is connected to the RF interface circuitry 1240 via a hermetic feedthrough (not shown in FIG. 12D).

[0096] As noted, the stimulating assembly 1216 is configured to be at least partially implanted in the user’s cochlea. The stimulating assembly 1216 includes a plurality of longitudinally spaced intra-cochlear electrical stimulating contacts (electrodes) 1244 that collectively form a contact array (electrode array) 1246 for delivery of electrical stimulation (current) to the recipient’s cochlea. The stimulating assembly 1216 extends through an opening in the recipient’s cochlea (e.g., cochleostomy, the round window, etc.) and has a proximal end connected to stimulator unit 1242 via lead region 1236 and a hermetic feedthrough (not shown in FIG. 12D). Lead region 1236 includes a plurality of conductors (wires) that electrically couple the electrodes 1244 to the stimulator unit 1242. The implantable component 1212 also includes an electrode outside of the cochlea, sometimes referred to as the extra-cochlear electrode (ECE) 1239.

[0097] As noted, the cochlear implant system 1202 includes the external coil 1208 and the implantable coil 1214. The external magnet 1250 is fixed relative to the external coil 1208 and the intemal / implantable magnet 1252 is fixed relative to the implantable coil 1214. The external magnet 1250 and the intemal / implantable magnet 1252 fixed relative to the external coil 1208 and the intemal / implantable coil 1214, respectively, facilitate the operational alignment of the external coil 1208 with the implantable coil 1214. This operational alignment of the coils enables the external component 1204 to transmit data and power to the implantable component 1212 via a closely-coupled wireless link 1248 formed between the external coil 1208 with the implantable coil 1214. In certain examples, the closely-coupled wireless link 1248 is an RF link. However, various other types of energy transfer, such as infrared (IR), electromagnetic, capacitive and inductive transfer, can be used to transfer the power and / or data from an external component to an implantable component and, as such, FIG. 12D illustrates only one example arrangement.

[0098] As noted above, the sound processing unit 1206 includes the external sound processing module 1224. The external sound processing module 1224 is configured to process the received input audio signals (received at one or more of the input devices, such as sound input devices 1218 and / or auxiliary input devices 1228) and convert the received input audio signals into output control signals for use in stimulating a first ear of a recipient or user (i.e., the external sound processing module 1224 is configured to perform sound processing on input signals received at the sound processing unit 1206). Stated differently, the one or more processors (e.g., processing element(s) implementing firmware, software, etc.) in the external sound processing module 1224 are configured to execute sound processing logic in memory toconvert the received input audio signals into output control signals (stimulation signals) that represent electrical stimulation for delivery to the recipient.

[0099] As noted, FIG. 12D illustrates an embodiment in which the external sound processing module 1224 in the sound processing unit 1206 generates the output control signals. In an alternative embodiment, the sound processing unit 1206 can send less processed information (e.g., audio data) to the implantable component 1212, and the sound processing operations (e.g., conversion of input sounds to output control signals 1256) can be performed by a processor within the implantable component 1212.[ooioo] In FIG. 12D, according to an example embodiment, output control signals (stimulation signals) are provided to the RF transceiver 1222, which transcutaneously transfers the output control signals (e.g., in an encoded manner) to the implantable component 1212 via the external coil 1208 and the implantable coil 1214. That is, the output control signals (stimulation signals) are received at the RF interface circuitry 1240 via the implantable coil 1214 and provided to the stimulator unit 1242. The stimulator unit 1242 is configured to utilize the output control signals to generate electrical stimulation signals (e.g., current signals) for delivery to the user’s cochlea via one or more of the stimulating contacts 1244. In this way, cochlear implant system 1202 electrically stimulates the user’s auditory nerve cells, bypassing absent or defective hair cells that normally transduce acoustic vibrations into neural activity, in a manner that causes the recipient to perceive one or more components of the input audio signals (the received sound signals).[ooioi] As detailed above, in the external hearing mode, the cochlear implant 1212 receives processed sound signals from the sound processing unit 1206. However, in the invisible hearing mode, the cochlear implant 1212 is configured to capture and process sound signals for use in electrically stimulating the user’s auditory nerve cells. In particular, as shown in FIG. 12D, an example embodiment of the cochlear implant 1212 can include a plurality of implantable sound sensors 1265(1), 1265(2) that collectively form a sensor array 1260, and an implantable sound processing module 1258. Similar to the external sound processing module 1224, the implantable sound processing module 1258 can comprise, for example, one or more processors and a memory device (memory) that includes sound processing logic. The memory device can comprise any one or more of: Non-Volatile Memory (NVM), Ferroelectric Random Access Memory (FRAM), read only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical / tangible memory storage devices. The one or moreprocessors are, for example, microprocessors or microcontrollers that execute instructions for the sound processing logic stored in memory device.

[0102] In the invisible hearing mode, the implantable sound sensors 1265(1), 1265(2) of the sensor array 1260 are configured to detect / capture input sound signals 1266 (e.g., acoustic sound signals, vibrations, etc.), which are provided to the implantable sound processing module 1258. The implantable sound processing module 1258 is configured to convert received input sound signals 1266 (received at one or more ofthe implantable sound sensors 1265(1), 1265(2)) into output control signals 1256 for use in stimulating the first ear of a recipient or user (i.e., the implantable sound processing module 1258 is configured to perform sound processing operations). Stated differently, the one or more processors (e.g., processing element(s) implementing firmware, software, etc.) in the implantable sound processing module 1258 are configured to execute sound processing logic in memory to convert the received input sound signals 1266 into output control signals 1256 that are provided to the stimulator unit 1242. The stimulator unit 1242 is configured to utilize the output control signals 1256 to generate electrical stimulation signals (e.g., current signals) for delivery to the user’s cochlea, thereby bypassing the absent or defective hair cells that normally transduce acoustic vibrations into neural activity.

[0103] It is to be appreciated that the above description of the so-called external hearing mode and the so-called invisible hearing mode are merely illustrative and that the cochlear implant system 1202 could operate differently in different embodiments. For example, in one alternative implementation of the external hearing mode, the cochlear implant 1212 could use signals captured by the sound input devices 1218 and the implantable sound sensors 1265(1), 1265(2) of sensor array 1260 in generating stimulation signals for delivery to the user.

[0104] According to the techniques of the present disclosure, the external sound processing module 1224 can also include an inertial measurement unit (IMU) 1270. The IMU 1270 is configured to measure the inertia of the user's head, that is, motion of the user's head. As such, the IMU 1270 comprises one or more sensors 1275 each configured to sense one or more of rectilinear or rotatory motion in the same or different axes. Examples of sensors 1275 that can be used as part of inertial measurement unit 1270 include accelerometers, gyroscopes, inclinometers, compasses, and the like. Such sensors can be implemented in, for example, micro electromechanical systems (MEMS) or with other technology suitable for the particular application.

[0105] As also illustrated in FIG. 12D, in certain examples, a second IMU 1280 including one or more sensors 1285 is incorporated into implantable sound processing module 1258 of implant body 1234. The second IMU 1280 can serve as an additional or alternative inertial measurement unit to the IMU 1270 of external sound processing module 1224. Uike sensors 1275, sensors 1285 can each be configured to sense one or more of rectilinear or rotatory motion in the same or different axes. Examples of sensors 1285 that can be used as part of inertial measurement unit 1280 include accelerometers, gyroscopes, inclinometers, compasses, and the like. Such sensors can be implemented in, for example, MEMS or with other technology suitable for the particular application. For hearing devices that include an implantable sound processing module, such as implantable sound processing module 1258, that includes an IMU, such as the IMU 1280, the techniques presented herein can be implemented without an external processor. Accordingly, a hearing device that includes an implant body 1234 and lacks an external component 1204 can be configured to implement the techniques presented herein.

[0106] As should be appreciated, while particular uses of the technology have been illustrated and described above, the disclosed technology can be used with a variety of devices in accordance with many examples of the technology. The above discussion is not meant to suggest that the disclosed technology is only suitable for implementation within systems akin to that illustrated in the figures. In general, additional configurations can be used to practice the processes and systems herein and / or some aspects described can be excluded without departing from the processes and systems disclosed herein.

[0107] This disclosure described some aspects of the present technology with reference to the accompanying drawings, in which only some of the possible aspects were shown. Other aspects can, however, be embodied in many different forms and should not be construed as limited to the aspects set forth herein. Rather, these aspects were provided so that this disclosure was thorough and complete and fully conveyed the scope of the possible aspects to those skilled in the art.

[0108] As should be appreciated, the various aspects (e.g., portions, components, etc.) described with respect to the figures herein are not intended to limit the systems and processes to the particular aspects described. Accordingly, additional configurations can be used to practice the methods and systems herein and / or some aspects described can be excluded without departing from the methods and systems disclosed herein.

[0109] According to certain aspects, systems and non-transitory computer readable storage media are provided. The systems are configured with hardware configured to execute operations analogous to the methods of the present disclosure. The one or more non-transitory computer readable storage media comprise instructions that, when executed by one or more processors, cause the one or more processors to execute operations analogous to the methods of the present disclosure.[oono] Similarly, where steps of a process are disclosed, those steps are described for purposes of illustrating the present methods and systems and are not intended to limit the disclosure to a particular sequence of steps. For example, the steps can be performed in differing order, two or more steps can be performed concurrently, additional steps can be performed, and disclosed steps can be excluded without departing from the present disclosure. Further, the disclosed processes can be repeated.[oom] Although specific aspects were described herein, the scope of the technology is not limited to those specific aspects. One skilled in the art will recognize other aspects or improvements that are within the scope of the present technology. Therefore, the specific structure, acts, or media are disclosed only as illustrative aspects. The scope of the technology is defined by the following claims and any equivalents therein.

[0112] It is also to be appreciated that the embodiments presented herein are not mutually exclusive and that the various embodiments can be combined with another in any of a number of different manners.

Claims

CLAIMSWhat is claimed is:

1. A method, comprising: monitoring a clinical session during which one or more operational settings of a medical device are configured; and generating, with an artificial intelligence (Al) model, a synchronous clinical record based on the monitoring.

2. The method of claim 1, further comprising: generating, based on the monitoring, a contemporaneous activity log associated with the clinical session.

3. The method of claim 2, wherein generating, with the Al model, the synchronous clinical record based on the monitoring comprises: applying the Al model to process the contemporaneous activity log.

4. The method of claim 2, wherein the synchronous clinical record comprises one or more summaries of the contemporaneous activity log.

5. The method of claim 4, wherein the one or more summaries follow a standardized format.

6. The method of claim 2, wherein the contemporaneous activity log comprises descriptions of one or more contemporaneous activities monitored in the clinical session or clinical information related to the clinical session.

7. The method of claim 6, wherein the one or more contemporaneous activities comprise activities pertaining to at least one of operation or management of the medical device or one or more tests performed during the clinical session.

8. The method of claim 6, wherein the clinical information related to the clinical session comprises one or more results of tests performed during the clinical session, one or more preferences of a recipient, recipient feedback, observations recorded by a medical practitioner, medical history of the recipient, performance data related to the medical device, or remote monitoring capabilities associated with the medical device.

9. The method of claim 6, wherein the synchronous clinical record is reflective of the one or more contemporaneous activities.

10. The method of claim 6, further comprising: selecting a subset of the descriptions of the one or more contemporaneous activities based on a user prompt; and applying the Al model to process the subset of the descriptions.

11. The method of claim 1, 2, 3, 4, 6, 7, 8, 9, or 10, wherein the medical device is a cochlear implant.

12. The method of claim 1, 2, 3, 4, 6, 7, 8, 9, or 10, wherein the medical device is an insulin pump.

13. The method of claim 1, 2, 3, 4, 6, 7, 8, 9, or 10, wherein the medical device is a hearing aid.

14. The method of claim 1, 2, 3, 4, 6, 7, 8, 9, or 10, wherein the medical device is a bone conduction device.

15. The method of claim 1, 2, 3, 4, 6, 7, 8, 9, or 10, further comprising: adjusting the one or more operational settings of the medical device during the clinical session.

16. The method of claim 1, 2, 3, 4, 6, 7, 8, 9, or 10, further comprising: providing the synchronous clinical record to a user; receiving feedback from the user in relation to the synchronous clinical record; and applying the Al model to update the synchronous clinical record based on the feedback from the user.

17. The method of claim 1, 2, 3, 4, 6, 7, 8, 9, or 10, further comprising: adapting a language of the clinical record to a selected user.

18. A method, comprising: obtaining a user prompt from a user; obtaining a contemporaneous activity log captured during a hearing device fitting session; and generating, by an artificial intelligence (Al) model, a clinical summary of the fitting session based on the user prompt and the contemporaneous activity log.

19. The method of claim 18, wherein obtaining the contemporaneous activity log comprise: monitoring the hearing device fitting session during which one or more operational settings of the hearing device are determined.

20. The method of claim 18, further comprising: training the Al model using a plurality of historical activity logs.

21. The method of claim 18, wherein generating, by the Al model, the clinical summary of the fitting session comprises: generating the clinical summary based on the user prompt.

22. The method of claim 18, 19, 20, or 21, further comprising: providing the clinical summary to the user; obtaining a modified user prompt from the user; and providing a modified clinical summary to the user based on the modified user prompt.

23. The method of claim 22, wherein providing the modified clinical summary to the user based on the modified user prompt comprises: processing the contemporaneous activity log, by the Al model, based on the modified user prompt.

24. The method of claim 18, 19, 20, or 21, wherein the Al model comprises a large language model (LLM).

25. The method of claim 18, 19, 20, or 21, wherein the user prompt is provided through a user interface.

26. A method, comprising: obtaining a user prompt from a user; processing, by an artificial intelligence (Al) model, a contemporaneous activity log associated with a clinical session based on the user prompt; and generating, by the Al model, a synchronous clinical record based on the processing.

27. The method of claim 26, wherein the synchronous clinical record comprises one or more clinical summaries or one or more recommendations.

28. The method of claim 26 or 27, wherein the one or more clinical summaries or the one or more recommendations follow a standardized format.

29. The method of claim 28, wherein the standardized format is established through a template.

30. The method of claim 26 or 27, further comprising: configuring one or more operational settings of a medical device based on the synchronous clinical record.

31. The method of claim 26 or 27, further comprising: outputting, the synchronous clinical record, to the user.

32. The method of claim 26 or 27, further comprising: transmitting the synchronous clinical record to an electronic health records software application.

33. The method of claim 32, wherein transmitting the synchronous clinical record to the electronic health records software application comprises: transmitting the synchronous clinical record to the electronic health records software application using an application programming interface (API).

34. One or more non-transitory computer readable storage media comprising instructions that, when executed by a processor, cause the processor to: obtain a contemporaneous activity log of a clinical session; generate, by an artificial intelligence (Al) model, a synchronous clinical record based on the contemporaneous activity log; and configure one or more operational settings of a medical device based on the synchronous clinical record.

35. The one or more non-transitory computer readable storage media of claim 34, wherein the contemporaneous activity log is captured during the clinical session.

36. The one or more non-transitory computer readable storage media of claim 34, wherein the one or more operational settings pertain to at least one of operation or management of the medical device.

37. The one or more non-transitory computer readable storage media of claim 34, wherein the synchronous clinical record comprises one or more clinical summaries or one or more recommendations .

38. The one or more non-transitory computer readable storage media of claim 34, 35, 36, or 37, wherein the one or more clinical summaries or the one or more recommendations follow a standardized format.

39. The one or more non-transitory computer readable storage media of claim 34, 35, 36, or 37, further comprising instructions that, when executed by a processor, cause the processor to: process, by the Al model, the contemporaneous activity log based on a user prompt.

40. The one or more non-transitory computer readable storage media of claim 34, 35, 36, or 37, further comprising instructions that, when executed by a processor, cause the processor to: output the synchronous clinical record to a user in a user interface.

41. A system, comprising: a memory; and at least one processor operable coupled to the memory, wherein the at least one processor is configured to: generate a contemporaneous activity log of one or more clinical activities performed during a clinical session; apply an artificial intelligence (Al) model to generate a synchronous clinical record reflective of the contemporaneous activity log; and update the synchronous clinical record based on feedback from a user.

42. The system of claim 41, wherein the contemporaneous activity log comprises descriptions of one or more activities pertaining to a medical device monitored in the clinical session.

43. The system of claim 41, wherein the synchronous clinical record comprises one or more clinical summaries or one or more recommendations.

44. The system of claim 41, 42, or 43, further comprising: training the Al model using a plurality of labeled training data, wherein the plurality of labeled training data comprises a plurality of historical activity logs.

Images