Abstract: A robust human cell culture model permissive to both SARS-COV-2 variants and MERS-COV is critical for assessment and validation of antivirals. Human alveolar A549 cells are regarded as a valuable model for respiratory virus infection. SARS-COV-2 uses the angiotensin converting enzyme 2 (ACE2) receptor for viral entry and the transmembrane serine protease 2 (TMPRSS2) to prime the SARS-COV-2 spike protein. By contrast, MERS-COV utilizes the dipeptidyl peptidase 4 receptor (DPP4) to enter the target cells. Three of which are negligibly expressed in A549. Disclosed herein is a generation of a robust human cell model that carries DPP4, ACE2, and TMPRSS2 receptor expressions. By transducing Dpp4 into A549-ACE2plusC3 cells (ACE2+/TMPRSS2+), the resulting cells expressing DPP4, ACE2 and TMPRSS2 (“ACE2plusC3D4”) are highly susceptible to MERS-COV and SARS-CoV-2 omicron infection. This ACE2plusC3D4 cell model can be applied for evaluation of antiviral drugs and potentially developed for high-throughput screening.

Abstract: An insertion catheter for a circulatory support catheter having a circulatory support device carried by an elongate flexible catheter shaft. The insertion catheter comprises a tubular body with a distal portion configured to axially movably receive the circulatory support device. A diameter of the distal portion is greater than a diameter of a mid portion of the tubular body. The insertion catheter may be inserted into an introducer sheath for delivery of the MCS device. A distal end of the insertion catheter may be located distally of a distal end of the introducer sheath and distally of the arterial bifurcation. The distal portion of the insertion catheter containing the MCS device may be located distally of the bifurcation, with a distal end of the MCS device slightly offset from the distal end of the tubular body.

Abstract: A tapered medical access sheath can comprise an access sheath hub and an access sheath shaft extending distally from the access sheath hub. The access sheath shaft can comprise a first delivery lumen extending from a proximal end of the access sheath shaft to a side opening on a distal portion of the access sheath shaft, the first delivery lumen having a width configured to slidably receive a distal portion of a medical device disposed around a guidewire. The access sheath shaft can comprise a tapered distal end portion disposed distally of the side opening. A recess can extend along a longitudinal dimension of the tapered distal end portion from a proximal end to a distal end of the tapered distal end portion. The recess can be in fluid communication with the first delivery lumen and have a width smaller than the diameter of the first delivery lumen.

Abstract: A system includes at least one hardware processor and at least one memory storing instructions that cause the at least one hardware processor to perform operations. The operations include configuring a processing stack in an execution node process. The processing stack includes a telemetry application programming interface (API). At least one configuration of a trace event is retrieved using an API call received by the execution node process. Telemetry information of the trace even is collected using the telemetry API based on the at least one configuration. An event table is updated based on the telemetry information.

Abstract: Disclosed is a system and method of using an event loader to share application information. The method includes generating a first log information object indicating a consumer target where execution information generated by an application shared with a consumer account of a data exchange is written. The method includes generating a first event unloader based on the first log information object. The first event unloader is linked to the application using a mapping. The method includes sending, by a processing device, the execution information generated by the application to the consumer target using the first event unloader.

Abstract: A medical delivery sheath assembly can comprise a first hub portion comprising a first delivery lumen configured to slidably receive at least a portion of a first medical device, and a second hub portion comprising a second delivery lumen configured to slidably receive at least a portion of a second medical device. A longitudinal axis of the first delivery lumen and a longitudinal axis of the second delivery lumen can form an acute angle where a distal portion of the first hub portion and a distal portion of the second hub portion merge. A joint hub portion can be coupled to the distal portion of the first hub portion and the distal portion of the second hub portion. The joint hub portion can comprise a third delivery lumen configured to slidably receive corresponding portions of each the first medical device and the second medical device.

Abstract: Introducers and dilators that include expansion features configured to dilate expandable access sheaths, and expandable access sheaths, are described herein. The introducer can include an expansion feature disposed on an elongate shaft. The expansion feature can include a larger outer diameter than the distal end of the elongate shaft or another portion of the elongate shaft. The expansion feature can be configured to dilate a portion of an expandable access sheath when the elongate shaft is translated within the expandable access sheath. Expandable access sheaths can comprise expandable distal end portions configured to be maintained in a closed state by, for example, a tensioned cord portion disposed around a circumferential portion of the expandable distal end portion, a plurality of pleats comprising material configured to attract one another, a circumferential portion with a weakened joint, and/or a weakened portion on a sidewall of the expandable distal end portion.

Abstract: A medical device delivery system can comprise a delivery catheter and an in-line sheath, the delivery catheter being preloaded within the in-line sheath. The delivery catheter can comprise a catheter hub and a catheter shaft. The catheter shaft can comprise a proximal portion extending distally from the hub and slidably receiving a proximal narrow portion of a medical device, and a distal portion slidably receiving a distal wide portion of a medical device. The in-line sheath can comprise a sheath hub and a sheath shaft. The sheath shaft can comprise a proximal portion extending distally from the sheath hub and slidably receiving at least a portion of the proximal portion of the catheter shaft, and an expandable distal portion slidably receiving the distal portion of the catheter shaft.

Abstract: Disclosed is an execution information sharing system that duplicates execution information to a provider target (and other targets) as it is being loaded to a consumer target. A first log information object and a second log information object are generated. The first and second log information objects comprise information indicating a consumer target and information indicating a provider target respectively where execution information generated by an application shared with a consumer account of a data exchange is written. A first event unloader and a second event unloader are generated based on the first and second log information objects respectively, wherein the first and second event unloaders are both linked to the application using a mapping. In response to receiving execution information from the application, the execution information is forwarded to the consumer target and the provider target using the first event unloader and the second event unloader respectively.

Abstract: Provided herein are systems and methods for configuring extended telemetry metric data types. A system includes at least one hardware processor coupled to a memory and configured to detect an API call at an execution node of a database system. Metric data emitted by a telemetry API corresponding to the API call is collected. The metric data is converted from a first data format associated with the telemetry API to a second data format to generate formatted metric data. The second data format is a native format to an event table of the database system. Telemetry data based on the formatted metric data is ingested into the event table.

Abstract: Several heart wall remodeling devices and methods are disclosed. One heart wall remodeling device includes an anchoring portion having an elongated anchor body with a distal anchor end portion and a proximal anchor end portion opposite the distal anchor end portion, a rotation joint portion having a distal joint end portion fixedly attached to the proximal anchor end portion and a proximal joint end portion opposite the distal joint end portion and a hemostasis element having a distal hemostasis end portion detachably connected to the proximal joint end portion. One heart wall remodeling device includes a tensioner that applies a variable tension between anchors.

Abstract: A system includes at least one hardware processor and at least one memory storing instructions that cause the at least one hardware processor to perform operations. The operations include configuring a processing stack in an execution node process. The processing stack includes a telemetry application programming interface (API). At least one configuration of a trace event is retrieved using an API call received by the execution node process. Telemetry information of the trace even is collected using the telemetry API based on the at least one configuration. An event table is updated based on the telemetry information.

Abstract: A delivery sheath comprises inter-connected fingers extending around a cylindrical inner lumen and forming one or more gaps. The inter-connected fingers may be configured to assume a default form in which the inner lumen has a first width, bend in response to an implant passing through the inner lumen to cause at least a portion of the inner lumen to increase beyond the first width, and/or elastically return to the default form following removal of the implant from the inner lumen.

Abstract: Methods and kits are described for testing for the presence or absence of any fungus in a sample. Examples of fungi that can be detected include, but are not limited to, those belonging to the genera Candida, Aspergillus and Pneumocystis. The methods include obtaining a sample suspected of containing fungal nucleic acid, including at least one universal region of fungal nucleic acid, and testing for the presence or absence in the sample of the at least one universal region of fungal nucleic acid. Samples may be biological or non-biological.

Abstract: Methods and kits are described for testing for the presence or absence of any fungus in a sample. Examples of fungi that can be detected include, but are not limited to, those belonging to the genera Candida, Aspergillus and Pneumocystis. The methods include obtaining a sample suspected of containing fungal nucleic acid, including at least one universal region of fungal nucleic acid, and testing for the presence or absence in the sample of the at least one universal region of fungal nucleic acid. Samples may be biological or non-biological.

Abstract: This invention relates to methods and compositions comprising antibodies or fragments thereof comprising a targeting ligand and engineered cytotoxic cells comprising a targeting agent specific for the targeting ligand, for use in inducing cytotoxicity in a cancer cell, in delivering a cytotoxic cell to a cancer cell in a subject, and in treating cancer.

Abstract: Components for valve treatment systems are disclosed. Valve treatment systems can include a delivery system for an implantable device. The delivery system can include one or more of clasp control components slidably disposed on a catheter handle, a control element for opening and closing the implantable device, a catheter assembly with features to reduce friction with another catheter assembly, grips for attaching catheter assemblies to clamps, catheter assemblies with features that stiffen or provide variable stiffness, and catheter assemblies with one or more steering control lumens incorporated into a reinforcement layer.

Abstract: Disclosed is an execution information sharing system that writes execution information to a provider target (and other targets) in a secure manner. Execution information generated by an application may be written to a consumer stage, wherein the application is shared by a provider account of a data exchange with a consumer account that executes the application. A consumer exchange service (ES) of the data exchange may send a request to a copy service of the data exchange to copy the execution information from the consumer stage to the provider stage, wherein the consumer ES is a part of the data exchange and is protected from actions of the consumer account. A copy operation may be executed to copy the execution information from the consumer stage to the provider stage using the copy service of the data exchange. The execution information is ingested from the provider stage to a provider table.

Abstract: Disclosed is an execution information sharing system that duplicates execution information to a provider target (and other targets) as it is being loaded to a consumer target. A first log information object and a second log information object are generated. The first and second log information objects comprise information indicating a consumer target and information indicating a provider target respectively where execution information generated by an application shared with a consumer account of a data exchange is written. A first event unloader and a second event unloader are generated based on the first and second log information objects respectively, wherein the first and second event unloaders are both linked to the application using a mapping. In response to receiving execution information from the application, the execution information is forwarded to the consumer target and the provider target using the first event unloader and the second event unloader respectively.

Abstract: Provided herein are systems and methods for configuring trace events. A system includes at least one hardware processor coupled to a memory and configured to instantiate a user code runtime to execute user-defined function (UDF) code. The user code runtime is instantiated within a sandbox process of an execution node. An application programming interface (API) call is detected during execution of the UDF code. The API call includes one or more configurations of a trace event. Telemetry information is collected based on the one or more configurations. The telemetry information is associated with the trace event using a telemetry API. The telemetry API corresponds to the API call. The telemetry information is formatted using the telemetry API, to generate structured telemetry information. The at least one hardware processor causes ingestion of the structured telemetry information into an event table.