~.
`(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)
`(19) World Intellectual Property
`>
`Organization
`en)
`International Bureau
`
`TUETAA
`
`(10) International Publication Number
`WO 2022/182756 Al
`
`==
`
`——
`WIPO( PCT
`
`(43) International Publication Date
`01 September 2022 (01.09.2022)
`
`(51) International Patent Classification:
`A61M 21/02 (2006.01)
`AGIN 1/36 (2006.01)
`
`(21) International Application Number:
`PCT/U$2022/017517
`
`(22) International Filing Date:
`
`(25) Filing Language:
`
`(26) Publication Language:
`
`23 February 2022 (23.02.2022)
`
`(81)
`
`English
`
`English
`
`Golden Valley, Minnesota 55416 (US). FELLOWS,Dono-
`van, 5500 Wayzata Boulevard, Suite 1600, Golden Valley,
`Minnesota 55416 (US).
`
`(74)
`
`Agent: GRUNZWEIG,Paul S. et al.; 100 South Fifth
`Street, Suite 2250, Minneapolis, Minnesota 55402 (US).
`
`Designated States (uiless otherwise indicated, for every
`kind of national protection available). AE, AG, AL, AM,
`AO, AT, AU, AZ, BA, BB, BG, BH, BN, BR, BW, BY, BZ,
`CA, CH, CL, CN, CO, CR, CU, CZ, DE, DJ, DK, DM, DO,
`DZ, EC, EE, EG, ES, FI, GB, GD, GE, GH, GM, GT, HN,
`HR, HU,ID,IL, IN,IR, IS, IT, JM, JO, JP, KE, KG, KH,
`KN,KP, KR, KW, KZ, LA, LC, LK, LR, LS, LU, LY, MA,
`MD,ME, MG, MK, MN, MW, MX, MY, MZ, NA,NG,NI,
`NO, NZ, OM,PA, PE, PG, PH, PL, PT, QA, RO, RS, RU,
`RW,SA, SC, SD, SE, SG, SK, SL, ST, SV, SY, TH, TJ, TM,
`TN. TR, TT, TZ, UA, UG, US, UZ, VC, VN, WS, ZA, ZM,
`ZW.
`
`(84)
`
`Designated States (unless otherwise indicated, for every
`kind of regional protection available): ARIPO (BW,GII,
`GM,KE, LR, LS, MW, MZ, NA, RW,SD, SL, ST, SZ, TZ,
`UG, ZM, ZW), Eurasian (AM, AZ, BY, KG, KZ, RU, TJ,
`TM), European (AL, AT, BE, BG, CII, CY, CZ, DE, DK,
`EE, ES, FL FR, GB, GR, HR, HU, IE, IS, IT, LT, LU, LV,
`
`(30) Priority Data:
`63/152,672
`
`23 February 2021 (23.02.2021) US
`
`INC.
`INSPIRE MEDICAL SYSTEMS,
`(71) Applicant:
`[US/US]; 5500 Wayzata Boulevard, Suite 1600, Golden
`Valley, Minnesota 55416 (US).
`
`(72)
`
`Inventors: MAIRS, Nicholas, 5500 Wayzala Boulevard,
`Suite 1600, Goldcn Valley, Minncsota 55416 (US). BEL-
`LAND, Brody, 5500 Wayzata Boulevard, Suite 1600,
`Golden Valley, Minnesota 55416 (US). LEE, Kent; 5500
`Wayzata Boulevard, Suite 1600, Golden Valley, Minncso-
`ta 55416 (US). RONDONI, John; 5500 Wayzata Boule-
`vaid, Suile 1600, Golden Valley, Mimesota 55416 (US).
`VEICHT, Aaron, 5500 Wayzata Boulcvard, Suite 1600,
`
`(54) Title: INTEGRATING STIMULATION THERAPY, PATIENT MANAGEMENT, AND EXTERNAL PATIENT MONI-
`TORING
`
`3216
`
`
`2100
`
`
`
`
`
`
`nn,
`Se,
`SECOND
`
`
`
`4227 < MA
`
`!
`
`
`
`gsource f
`
`31304
`
`
`
`(57) Abstract: A method and system for integrating stimulation therapy, patient management, and extemal patient monitoring.
`
`[Continued on nextpage]
`
`
`
`wo2022/182756AIIIIMIMINNNINIRTTTAAATA
`
`

`

`WO 2022/182756 AA |IITIMNUIINNMOUN EIN TTAOTAMT
`
`MC, MK, MT, NL, NO, PL, PT, RO, RS,SE, SI, SK, SM,
`TR), OAPT(BF, BJ, CF, CG, Cl, CM, GA, GN, GQ, Gw,
`KM,ML, MR,NE, SN, TD, TG).
`
`Published:
`
`— with international search report (Art. 21(3)
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`INTEGRATING STIMULATION THERAPY, PATIENT MANAGEMENT, AND
`
`EXTERNAL PATIENT MONITORING
`
`Background
`
`[0001] Some implantable medical devices may communicate with external
`
`devices to provide information regarding operation of the implantable medical
`
`device within the patient, status of the patient, and the like.
`
`Brief Description of the Drawings
`
`[0002] FIG. 1 is a block diagram schematically representing an example patient
`
`management system including a patient virtual check-in portion.
`
`[0003] FIGS. 2-7 are each a diagram schematically representing example
`
`patient management Clinician user interfaces.
`
`[0004] FIG. 8 is a block diagram schematically representing a patient survey.
`
`[0005] FIG. 9 is a block diagram schematically representing an example control
`
`portion.
`
`[0006] FIG. 10 is a block diagram schematically representing an example user
`
`interface.
`
`[0007] FIG. 11 is a block diagram schematically representing an example patient
`
`managementsystem.
`
`[0008] FIG. 12 is a block diagram schematically representing an example patient
`
`managementengine.
`
`[0009] FIG. 13 is a diagram schematically representing an example patient
`
`managementuserinterface including nightly utilization information tools.
`
`[0010] FIG. 14 is a diagram schematically representing an example patient
`
`managementuserinterface including therapy effectiveness and outcomes.
`
`[0011] FIG. 15A is a block diagram of an example patient device including a
`
`patient app.
`
`[0012] FIG. 15B is a block diagram of an example patient survey engine.
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`[0013] FIG. 16 is a flow diagram schematically representing an example method
`
`of patient management.
`
`[0014] FIG. 17A is a block diagram schematically representing an example
`
`control portion.
`
`[0015] FIG. 17Bis a block diagram schematically representing an example user
`
`interface.
`
`[0016] FIG. 18 is a block diagram schematically representing an example
`
`method (and/or example device) for patient care in treating sleep disordered
`
`breathing (SDB), which includes aspects of patient management, stimulation
`
`therapy, and third party diagnostic/monitoring.
`
`[0017] FIG. 19 is a block diagram schematically representing example sensing
`
`parameters associated with at least a third party diagnostic/monitoring portion.
`
`[0018] FIG. 20 is a block diagram schematically representing example
`
`determined parameters associated with at least a third party
`
`diagnostic/monitoring portion.
`
`[0019] FIG. 21 is a block diagram schematically representing an example
`resource.
`
`[0020] FIG. 22 is a block diagram schematically representing an example
`
`method (and/or example device) for integrating a patient managementinput and
`
`a third-party diagnostic/monitoring input into stimulation therapy.
`
`[0021] FIG. 23 is a block diagram schematically representing an example
`
`method (and/or example device) for integrating a stimulation therapy input and a
`
`third-party diagnostic/monitoring input into patient management.
`
`[0022] FIG. 24A is a block diagram schematically representing an example
`
`stimulation therapy portion.
`
`[0023] FIG. 24B is a block diagram schematically representing an example
`
`patient managementportion.
`
`[0024] FIG. 25 is a block diagram schematically representing an example
`
`method (and/or example device) for stimulation therapy including closed-loop
`
`feedback from a patient managementinput and a third-party
`
`diagnostic/monitoring input.
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`[0025] FIG. 26 is a block diagram schematically representing an example
`
`method (and/or example device) for patient management including closed-loop
`
`feedback from a stimulation therapy input and a third-party
`
`diagnostic/monitoring input.
`
`[0026] FIG. 27A is a block diagram schematically representing an example
`
`control portion.
`
`[0027] FIG. 27B is a block diagram schematically representing an example user
`
`interface.
`
`[0028] FIG. 28 is a flow diagram schematically representing an example method
`
`of patient care for treating sleep disordered breathing (SDB).
`
`Detailed Description
`
`[0029] In
`
`the
`
`following detailed description,
`
`reference
`
`is made
`
`to
`
`the
`
`accompanying drawings which form a part hereof, and in which is shown by way
`
`ofillustration specific examples in which the disclosure may be practiced.
`
`It is to
`
`be understood that other examples may be utilized and structural or logical
`
`changes may be made without departing from the scope of
`
`the present
`
`disclosure. The following detailed description, therefore, is not to be taken in a
`
`limiting sense.
`
`It is to be understood that features of the various examples
`
`described herein may be combined,
`
`in part or whole, with each other, unless
`
`specifically noted otherwise.
`
`[0030] At
`
`least some examples of
`
`the present disclosure are directed to
`
`integrating information from different Sources and/or pathways, etc. to enhance
`
`patient care in treating sleep disordered breathing (SDB).
`
`In some such
`
`examples,
`
`the different sources and/or pathways may comprise patient
`
`management
`
`information, stimulation therapy information, and/or third party
`
`diagnostic/monitoring information.
`
`In
`
`some examples,
`
`integrating such
`
`information may enhance efficacy of stimulation therapy and/or of patient
`
`management.
`
`The third party diagnostic/monitoring information may be
`
`obtained
`
`from third
`
`party
`
`diagnostic/monitoring
`
`devices, which may
`
`communicate with the devices used to perform patient management and/or
`
`3
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`devices used to perform stimulation therapy.
`
`It will be understood that at least
`
`some examples of
`
`the present disclosure use the disparate sources of
`
`information as a close loop feedback to take actions, such as delivering
`
`Stimulation
`
`therapy,
`
`performing
`
`patient management
`
`actions,
`
`adjusting
`
`Monitoring, and the like. Moreover, each action in turn, may produce further
`
`feedback communicated to the various devices and therapy, monitoring,
`
`management elements hosted among or On such devices.
`
`[0031] At
`
`least some examples of
`
`the present disclosure are directed to
`
`facilitating patient care.
`
`In some examples, a method and/or system to facilitate
`
`patient care may comprise
`
`arrangements which provide for enhanced
`
`communication and workflows between and among: (1) a patient and a clinician
`
`regarding the status or progress of their therapy and/or evaluation as a patient
`
`candidate; and (2) multiple clinicians (e.g. caregiver entities) forming a patient
`
`care team.
`
`In some examples, a device manufacturer or device service provider
`
`may also communicate via such workflows with the care team and/or the patient
`
`to facilitate patient care and clinician performance.
`
`[0032] Among other aspects,
`
`the example methods and/or systems may
`
`comprise a virtual check-in, which is engageable on a mobile app (on a user
`
`interface of a computing device) and which provides feedback from the patient
`
`to the clinician regarding their usage and experience in using a therapy device.
`
`Oncereceived, this patient data may at last partially drive clinician workflows on
`
`user interfaces adapted to facilitate patient care for a plurality of patients.
`
`Among other features, these workflows driven via user interfaces mayfacilitate
`
`a clinician in quickly identifying patients which warrant faster or deeper attention
`
`to help the patient achieve desirable treatment outcomes.
`
`Similarly,
`
`these
`
`workflows (via the user interfaces) facilitate Communication and coordination
`
`among members (e.g. clinicians) of the care team which represent different
`
`types of entities (e.g. sleep study center, medical clinic, surgical facility, etc.)
`
`treating the patient.
`
`[0033] These features and attributes, and additional features and attributes, are
`
`described below in association with at least FIGS. 1-10.
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`[0034] At
`
`least some examples of the present disclosure are directed to a
`
`method and/or apparatus to perform patient care, patient management, and the
`
`like.
`
`In some examples, a method and/or system to facilitate patient care may
`
`comprise arrangements which provide for enhanced communication and patient
`
`management between and among: (1) a patient and a clinician regarding the
`
`status or progress of their therapy and/or evaluation as a patient candidate; and
`
`(2) multiple clinicians (e.g. Caregiver entities) forming a patient care team.
`
`In
`
`some examples, a device manufacturer or device service provider may also
`
`communicate with the care team and/or the patient to facilitate patient care and
`
`clinician performance.
`
`In some examples, the device manufacturer or device
`
`service provider also may operate, supply, maintain a processing resource (e.g.
`
`cloud server) to provide an arrangement, framework, pathway, etc. by which
`
`patient management may be performed with
`
`related information being
`
`displayable on a user interface such as, but notlimited to, a clinician portal.
`
`[0035] It will be understood that the term clinician may refer to a device therapy
`
`technician, sleep study technician, a physician, or other medical worker(e.g.
`
`health care professional) suitably experienced to perform (or assist with) the
`
`example methods and systems of patient management and care of the present
`
`disclosure.
`
`[0036] In some instances, the example methods and/or systems may comprise
`
`displaying at
`
`least some patient management information and tools (and/or
`
`device managementinformation and tools) via a user interface (e.g. graphical
`
`user interface), such as on a desktop workstation, mobile computing tablet (or
`
`other convenient mobile computing device).
`
`[0037] In some examples, one aspect of the example methods and/or systems
`
`of patient management may comprise a patient remote control communicating
`
`its usage information wirelessly via a patient app (e.g. on a mobile device) to a
`
`clinician portal. Via such arrangements, the clinician may receive patient usage
`
`information very quickly, and in a manner convenientto the patient because the
`
`usage information may be sent from the patient's home, etc. The clinician may
`
`receive this usage information after each night’s use of the stimulation therapy
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`such that, with regard to at least nightly usage metrics, the clinician is kept up to
`
`date on a near real-time basis.
`
`[0038] This arrangement stands in
`
`sharp contrast
`
`to some commercially
`
`available systems which may communicate usage information from a patient
`
`remote control by requiring the patient to bring their patient remote control to a
`
`facility at which the usage information may be downloaded,
`
`transferred, etc.
`
`from the patient remote control to the clinician computing device for viewing on
`
`a clinician portal.
`
`In such commercially available arrangements, a clinician
`
`would receive updates regarding patient usage considerably less frequently and
`
`less conveniently than the nightly usage data available each day in the various
`
`examples of the present disclosure.
`
`[0039] At least some examples of the present disclosure provide tools to obtain
`
`information about how and when a patientvolitionally utilizes stimulation therapy
`
`based on the times and days that the patient turns the therapy on and off. This
`
`information provides objectivity regarding when a patient starts, pauses, and/or
`
`ends nightly therapy, among other information such as stimulation amplitude
`
`changes, and the like.
`
`In some examples, this objective information may be
`
`displayed in a userinterface (viewable by a clinician) together with subjective
`
`information, such as a patient’s subjective experience during nightly stimulation
`
`therapy, after such therapy (e.g. during the daytime), and the like. By providing
`
`both the objective information and the subjective information juxtaposed (or
`
`otherwise located nearby) in a user interface, a clinician may enhance their
`
`ability to discern relationships between stimulation therapy settings, volitional
`
`patient usage (or non-usage) of the stimulation therapy, patient symptoms, and
`
`the like. The discernment of such relationships may,
`
`in turn, inform decisions
`
`resulting in changesto stimulation therapy parameters or resulting in no change
`
`to stimulation therapy parameters, among other considerations.
`
`[0040] Accordingly, via at
`
`least some of
`
`these examples, a clinician may
`
`efficiently and effectively become informed of the status, progress, health of
`
`their patients, which may contribute to patient adherence, therapy efficacy, and
`
`improved patient outcomes.
`
`By providing patient stimulation therapy usage
`
`information on such a timely basis, the example patient management systems
`
`6
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`and methods also may facilitate a clinician in making interventions, patient
`
`education/encouragement, etc. within a time frame more likely to maintain or
`
`improve a trajectory of successful patient adherence, therapy efficacy, and/or
`
`patient outcomes.
`
`At
`
`least some example interventions include adjusting
`
`stimulation therapy settings and then application of the modified stimulation
`
`settings during delivery of stimulation therapy to the patient (via the IMD) during
`
`a nightly therapy period.
`
`[0041] Moreover,
`
`in some such examples, while the example display tools (e.g.
`
`available within a user
`
`interface) may inform the clinician in evaluating
`
`stimulation therapy treatment decisions, the example display tools still provide
`
`the clinician with appropriate autonomy in making medical decisions and/or
`
`using their discretion as appropriate regarding adjustment of parameters of the
`
`programmer, IMD, etc.
`
`[0042] These examples, and additional examples, are described in association
`
`with at least FIGS. 11-17B.
`
`[0043] FIG.
`
`1
`
`is a block diagram schematically representing an example
`
`arrangement 200, deployable in a method or as a system,
`
`to solicit, manage,
`
`sort, and communicate patient information to facilitate patient care. As shown in
`
`FIG. 1, example arrangement 200 may comprise an array 202 of computing
`
`devices 210, each of which host a patient app 212 relating to patient care. The
`
`patient app 212 may provide patient education, enable communication with a
`
`caregiver, device servicer, device manufacturer, etc.
`
`In some such examples,
`
`at
`
`least some of the computing devices 210 comprise a mobile computing
`
`device, such as a mobile phone,
`
`tablet, smartwatch, etc. which has a user
`
`interface (e.g. 1070 in FIG. 10) to provide for operation of, and display of, the
`
`patient app 212. As further shown in FIG. 1,
`
`in some examples the patient app
`
`212 may comprise a virtual check-in app or function 220 to facilitate a patient
`
`checking in with a caregiver, such as a Clinician. Among other functions and
`
`features, the virtual check-in app 220 may comprise a patient survey 223, which
`
`leads the patient through a series of questions (i.e. queries) regarding their use
`
`of their therapy device, how often they use the device, what may be preventing
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`them from using the device, and the like. At least some example queries are
`
`later described further in association with at least FIGS. 7 and 8.
`
`[0044] As further shown in FIG. 1, the devices 210 may communicate with other
`
`devices, entities, etc. via cloud 230 via a wireless communication protocol as
`
`represented by directional arrows 227 and/or wired communication protocol in
`
`some examples.
`
`It will be understood that cloud 230 may comprise a computing
`
`resource, including programming, provided via a third party to provide, support,
`
`and manage the patient managementapp for the care entities 250A-250C and
`
`the patient app 212 for the patients, which facilitates patient care and facilitates
`
`coordinated interaction among the care entities 250A-250C with each other and
`
`the respective patients.
`
`In some examples, cloud 230 may comprise at least a
`
`portion or, and/or an example implementation of, the control portion 1050 (FIG.
`
`9) and userinterface 1070 FIG. 10).
`
`In some examples, the cloud 230 may be
`
`provided via a device manufacturer or servicer, or third party contracted by a
`
`device manufacturer. The cloud 230 may be hostedvia the internet, world wide
`
`web, and/or other network communication link.
`
`[0045] As further shown in FIG. 1, example arrangement 200 may comprise an
`
`array 240 of entities 250A, 250B, 250C, which provide care in some manner to a
`
`patient associated with one of the devices 210. The entities 250A, 250B, 250C
`
`may work together in at least some aspects to help coordinate care for the
`
`patient(s). Each entity may provide a particular form of expertise in patient care,
`
`such examples in which one entity 250A comprises a medical clinic, another
`
`entity 250B comprises a sleep center, and other entities supportive of patient
`
`care 250C. There may greater or fewer than three entities which form at least
`
`part of a care team.
`
`[0046] Each entity 250A-250C comprises a computing resource, such as
`
`workstation or other computing device which may be stationary or mobile,
`
`including a userinterface (e.g. 1070 in FIG. 10) to support operation and display
`
`of a clinician portal 260. Among other functions and features, the clinician portal
`
`260 may comprise a patient management app 270 by which the particular care
`
`provider (e.g. medicalclinic, sleep center, etc.) may manage patient care among
`
`a group of patients, for an individual patient, etc. The patient management app
`
`8
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`270 also may enable communicating with other entities (e.g. among 250A-
`
`250C) regarding patient care of the patients associated with devices 210.
`
`In
`
`some examples, the entities 250A-250C may communicate with each other via
`
`cloud 230 (e.g. network communication link, internet, web, etc.) as represented
`
`via indicators 227.
`
`[0047] At least some features and attributes of the patient management app 270
`
`and/or patient app 212 are further described in association with FIGS. 2-10.
`
`[0048] FIGS. 2-7 are diagrams schematically representing several example user
`
`interfaces, such as graphical user interfaces, displayable on a display screen
`
`associated with a computing device which may be mobile (e.g. phone, tablet,
`
`etc.) or stationary (e.g., desktop, workstation, etc.).
`
`In some examples, the user
`
`interfaces in FIGS. 2-7 may comprise example implementations of the patient
`
`management app 260 operable and displayable as a user interface on clinician
`
`portal 260, as described in association with FIG. 1. Accordingly, these example
`
`user interfaces in FIGS. 2-7 also comprise example implementations of the
`
`control portion 1050 in FIG. 9 and/or user interface 1070 in FIG. 10.
`
`[0049] It will be further understood that the arrangementof the various portions
`
`displayed on each respective example user interface and/or the detailed listings
`
`within each respective displayed portion may act as a workflow method which a
`
`Clinician (and/or a patient in some instances) may perform to advance patient
`
`care. Similarly,
`
`it will be apparent from FIG.
`
`1 and the user interfaces in FIGS.
`
`2-7, and the engines, control portions, etc.
`
`in association with FIGS. 8-10, that
`
`the various features, arrangements, components, etc. may be embodied as a
`
`system or apparatus.
`
`[0050] FIG. 2 is a block diagram schematically representing an example user
`
`interface 400 for patient care, and which may comprise one example
`
`implementation of the patient management app 260 (FIG. 1), control portion
`
`1050 (FIG. 9), and/or user interface 1070 (FIG. 10). As shown in FIG. 2, the
`
`user interface 400 comprises a banner including a patient function selector 410,
`
`among other function selectors (¢.g. practice, help, etc.). With the patient
`
`function selected, one example user interface 400 comprises a therapy user
`
`interface function 412 and an evaluation user interface function 414.
`
`FIG. 2
`
`9
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`represents an example implementation upon selection of the evaluation function
`
`414, which includes patient information 420 and visit information 450 for a group
`
`421 of example patientlistings 422 (e.g. patient record). Each patientlisting
`
`422 comprises, under patient information 420, a name, date,
`
`ID, de-identified
`
`ID, and whether or not the patient has linked (426) via the app to the patient
`
`management app 260 (at care entities 250A-250C) and the cloud 230.
`
`It will be
`
`further understood that each patient listing 422 may comprise visit information
`
`450, such as a date and type (e.g. Initial consult, ENT consult, etc.) of a Last
`
`Visit 452 and/or a date and type (e.g. ENT consult, Airway exam, etc. of a Next
`
`Visit 454.
`
`It will be understood, of course, that for the many different types of
`
`patient care which may be provided, the types of visit may vary greatly and
`
`accordingly the types of visits (e.g. ENT consult, Ainway exam) shown here are
`
`merely examples and are notlimiting.
`
`[0051] As further shown in FIG. 2 via the bolded box 423 outlining the second
`
`patient listing, a caregiver (e.g. clinician) may select a particular patient for
`
`further review, with at least some of those details being illustrated and described
`
`in association with FIGS. 2-8.
`
`[0052] As further shown in FIG. 2, the user interface 400 may comprise a sort
`
`function 460 and/or a flag function 462.
`
`In some examples, the sort function
`
`460 may enable a clinician to sort the patient listings 422 according to various
`
`criteria,
`
`including which types of visits they had and/or the date on which the
`
`visit occurred.
`
`In some examples, the sort function 460 may be implemented
`
`automatically by which the user interface 400 automatically sorts the patient
`
`listings according to criteria pre-selected by the clinician and/or device
`
`manufacturer, etc. As a result, upon the clinician opening the user interface
`
`400, the patient listings 422 may already be sorted according to the clinicians
`
`preferred criteria. Among other features,
`
`this arrangement may help the
`
`clinician quickly determine which patients the clinician would like to assessfirst
`
`or last, etc.
`
`[0053] In some examples,
`
`the sort
`
`function 460 may perform its sorting
`
`according to which patient listings are flagged (per flag function 462), with the
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`sort function 460 also having selection capabilities for which flags are to be
`
`sorted, in some examples.
`
`[0054] As further shown in FIG. 2, the user interface 400 may comprise a flag
`
`function 462, which may enable a clinician to quick spot patient listings 422
`
`which may warrant faster or more attention.
`
`The flag function 462 may
`
`comprise a manual selection feature by which the clinician may select a patient
`
`listing 422 to be flagged and/or may comprise an automatic selection feature by
`
`which the patient
`
`listings are automatically flagged according criteria pre-
`
`selected by the clinician and/or device manufacturer, etc. As a result, upon the
`
`clinician opening the userinterface 400, at least some of the patientlistings 422
`
`may already be flagged according to the clinicians preferred criteria based on
`
`the flag function 462. Among other features,
`
`this arrangement may help the
`
`clinician quickly determine which patients the clinician would like to assessfirst
`
`or last, etc.
`
`[0055] Among other criteria by which a patient listing may be sorted and/or
`
`flagged,
`
`the user interface 400 may enable sorting and/or flagging patient
`
`listings according to those patients which have missed appointments, are no
`
`longer seeking care, as well as other parameters further addressed in later
`
`Figures, such as the patient stopping use of
`
`the device, underutilization,
`
`discomfort, and the like.
`
`[0056] FIG. 3 is a block diagram schematically representing an example user
`
`interface 470, which comprises at least some of substantially the same features
`
`and attributes of the user interface 400 of FIG. 2, except being an example
`
`implementation of selection of
`
`the therapy function 412 (instead of
`
`the
`
`evaluation function 414). As shownin FIG. 3, user interface 470 comprises the
`
`same type of patient listings 422 regarding patient information 420 and visit
`
`information 450, except with the last visit 452 and next visit 454 information
`
`pertaining to therapy-related milestones
`
`instead of
`
`the evaluation-related
`
`milestones shownin FIG. 2. As shownin FIG. 3,
`
`in some examples at least
`
`some therapy-related milestones may be related to treating sleep disordered
`
`breathing (SDB), such “implant” and “activation and tuning”.
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`[0057] As further shown in FIG. 3, user interface 470 may further comprise, for
`
`each patientlisting, a “last virtual update” indicator 472, by which the clinician
`
`will become informed of a therapy effectiveness indication, usage indication, etc.
`
`to help the clinician determine which patients are doing well and which may
`
`warrant faster or deeper attention.
`
`In some such examples, the content of the
`
`indicator 472 for each patient
`
`listing 422 may be sorted (manually or
`
`automatically) per sort function 460 and/or may be flagged (manually or
`
`automatically) per flag function 462,
`
`in a manner similar to that previously
`
`described for user interface 400 in FIG. 2.
`
`[0058] FIG. 4 is a block diagram schematically representing an example user
`
`interface 600. As shownin FIG. 4, user interface 600 provides one example
`
`implementation of a user interface viewable by a clinician upon selecting, for
`
`further review, one of the patient listings 422 in user interfaces 400 (FIG. 2) or
`
`470 (FIG. 3). The particular patient listing 422 may be selected for ordinary
`
`review or because the particular patient
`
`listing 422 was brought
`
`to the
`
`immediate attention of the clinician because it was sorted and/or flagged (in the
`
`manner previously described)
`
`to become conspicuously noticeable to the
`
`clinician in viewing one of the userinterfaces 400, 470.
`
`[0059] As shownin FIG. 4, the user interface 600 comprises a banner 410 with
`
`a patient view selector 410, and an individual patient listing 610.
`
`In normal
`
`usage, the patient's name or other unique identifying information would belisted
`
`on user interface 600 at 610 or elsewhere.
`
`In some examples, the banner area
`
`also may comprise an evaluation indicator 612 to indicate that the patientlisting
`
`is displaying patient evaluation information, such as but not limited to evaluating
`
`whether the patient is suitable for a particular type of therapy.
`
`In the case of
`
`sleep disordered breathing, the evaluation may be regarding whetherthe patient
`
`is a suitable candidate for upper airway stimulation, CPAP, or other types of
`
`therapy. With this in mind, as shown in FIG. 4,
`
`in some examples, the user
`
`interface G00 may comprise a patient status portion/function 640 which includes
`
`a listing of several different evaluation milestones 642-652. Each milestone
`
`may correspond to a particular medical procedure, examination, consultation, or
`
`relate to other actions such as payment information (e.g. insurance accepted).
`
`12
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`Eachlisted milestone 642-652 also may comprise an indication of whether the
`
`particular milestone was completed.
`
`In one particular example, evaluation
`
`milestones relating to care for sleep disordered breathing (SDB) may comprise
`
`initial consultation (642), EarNoseThroat (ENT) consultation 644, Airway Exam
`
`(Drug Induced Sleep Endoscopy — DISE) 646, Insurance 648, Implant (surgical
`
`implantation of a therapy device) 650, and Activation and Tuning (of the
`
`implanted device) 652.
`
`[0060] Among other features, the patient status portion 640 of user interface 600
`
`conveniently provides a summary and sequence by which a clinician may
`
`immediately recognize which evaluation milestones (642-652) have been met by
`
`the patient and which milestones have yet to been achieved. Accordingly, the
`
`patient status portion 640 aids the clinician in quickly determining on what path
`
`to proceed to help this particular patient, and/or may help the clinician to quickly
`
`determine which care team member they should communicate to facilitate
`
`progression of the patient through the various milestones. As desired,
`
`the
`
`clinician may select one of the listed milestones 642-652 to be taken to another
`
`user interface screen to obtain more detailed information regarding the selected
`
`milestone. As an example, upon selection of the initial consult milestone 642,
`
`the clinician will be taken to user interface 670 in FIG. 5, which will be further
`
`described later.
`
`[0061] In Some examples,
`
`the patient status portion 640 also may facilitate
`
`patient care by the device manufacturer (or servicer) upon that entity becoming
`
`aware of certain milestones which a particular patient or a sampling of patients
`
`may have trouble achieving, and then take action to facilitate better outcomesin
`
`completing such milestones.
`
`[0062] However, with further reference to FIG. 4, user interface 600 also
`
`comprises a care team portion 620 which providesa listing 622 of the particular
`
`care team providers (e.g. entities 250A-250C in FIG. 1) which are caring for this
`
`particular patient. Accordingly, via this portion 620, a clinician may quickly
`
`determine the members of the care team.
`
`In some examples, portion 620 also
`
`may comprise an “app linked” function 426 to determine whether the patient
`
`and/or a care team member haslinked into the cloud 230 (and therefore the
`
`13
`
`

`

`WO 2022/182756
`
`PCT/US2022/017517
`
`patient management system).
`
`In some examples, portion 620 also comprises a
`
`share function 427 may enable initiation of sharing information with a care team
`
`member and/or confirmation of the ability of a care team membe