Dynamic display method, device, equipment and storage medium for registration date

Abstract

The present invention proposes a method, device, equipment, and storage medium for dynamically displaying registration dates. The method includes: generating a reference calendar based on target dates available for registration, splitting the reference calendar into weeks, and then determining target weekly blocks; determining the week numbers of each target date and then traversing the target weekly blocks one by one in order, wherein the second number of the reference weekly block is less than the first number of the adjacent weekly block, inserting the target date of the adjacent weekly block into the reference weekly block, deleting the adjacent weekly block, and updating the second number of the reference weekly block; arranging the target weekly blocks into a target weekly array and then rendering a target view. The method can dynamically determine the target date based on patient needs, determine the target weekly block from the weekly blocks split from the calendar, reduce the display of invalid dates by merging multiple fused weekly blocks, and reduce the display scale of the target view by reducing the number of weeks. Patients can view all target dates in one view, thereby improving patient experience.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method, device, equipment and storage medium for dynamically displaying a registration date. Background Art

[0002] At present, the technology for online appointment registration has become more and more mature. After the patient logs in to the hospital's mini program or APP, he selects the department he needs to visit and enters the appointment interface. After selecting the target date in the appointment interface, the information of each doctor scheduled on the target date and the corresponding number source are displayed. After the patient selects the number source, the registration is completed.

[0003] In the related art, there are two main ways to display the available registration dates on the appointment interface. One way is to display a horizontally draggable table, and the patient selects the date in the table. The other way is to display the available registration dates in a highlighted form on the calendar.

[0004] However, the first method has a limited number of available registration dates displayed in the table. When the number of scheduled dates is greater than the number of displayable dates, the patient needs to drag the table when making an appointment for a later target date, and then make a selection after the target date appears in the table. The second method is to read and determine the available registration dates in monthly units. If the monthly calendar only displays the dates of the current month, when the current date is at the end of the month and the number of remaining dates is less than the number of scheduled dates, the patient can only switch to the calendar of the next month when he wants to make an appointment for a later target date. Even if there are some calendar components that can fill the calendar of the current month with the dates of adjacent months, for example, if the last day of the month is Sunday, the first 6 dates of the same week of the next month can be displayed. If the target date is still after the seventh day, the patient still needs to switch to the calendar of the next month to operate. Therefore, the existing solution cannot intuitively display all available registration dates. Patients need to perform at least one operation to ensure that they know all available registration dates, which results in a poor operating experience. Summary of the Invention

[0005] The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, the present invention provides a method, apparatus, device, and storage medium for dynamically displaying registration dates. These methods can dynamically construct a display view of target dates, allowing patients to display all target dates without any manipulation, thereby improving the patient experience.

[0006] In a first aspect, an embodiment of the present invention provides a method for dynamically displaying a registration date, comprising:

[0007] Determine multiple target dates for registration based on the target department information obtained from the registration interface, and generate at least one reference calendar, wherein the reference calendar corresponds to the month in which the target date falls;

[0008] Splitting each reference calendar into initial weekly blocks in units of weeks, and determining the initial weekly block where the target date is located as the target weekly block;

[0009] Based on any of the target week blocks, determine the week numbers of the target dates, determine the first week number as the first number, and determine the last week number as the second number;

[0010] Traversing the target weekly blocks one by one in sequence, if the second serial number of the currently traversed reference weekly block is smaller than the first serial number of the next adjacent weekly block, inserting the target date of the adjacent weekly block into the reference weekly block based on the corresponding weekly serial number, deleting the adjacent weekly block, and updating the second serial number of the reference weekly block;

[0011] All the remaining target week blocks are arranged into a target week array based on the format of the reference calendar, a target view is rendered and displayed based on the target week array, and each target date is identified in the target view.

[0012] According to some embodiments of the present invention, determining multiple target dates for available registration based on target department information obtained from the registration interface includes:

[0013] Constructing a first option and a second option in the registration interface, wherein the first option includes multiple optional department information, and the second option includes multiple optional number source requirements, and the optional number source requirements are used to indicate the consultation time or the consultation doctor;

[0014] Obtaining the target department information selected in the first option, determining the department registration dates that are open for registration based on the target department information, and determining the selectable number sources corresponding to each of the department registration dates;

[0015] Obtaining the first signal source requirement selected in the second option, and screening a target signal source from the plurality of optional signal sources based on the first signal source requirement;

[0016] The department registration date corresponding to the target number source is determined as the target date.

[0017] According to some embodiments of the present invention, generating at least one reference monthly calendar includes:

[0018] determining the first of said target dates as a first date and determining the last of said target dates as a second date;

[0019] When the first date and the second date respectively correspond to the same month, the first date is input into a preset calendar component to generate a first calendar, and the first calendar is determined as the reference calendar;

[0020] Alternatively, when the first date and the second date correspond to different months, the first date is input into the calendar component to generate the first calendar, the second date is input into the calendar component to generate the second calendar, and at least one reference calendar is determined based on the first calendar and the second calendar.

[0021] According to some embodiments of the present invention, determining at least one reference calendar based on the first calendar and the second calendar includes:

[0022] Determine the last week of the first calendar month as a first reference week, and determine the first week of the second calendar month as a second reference week;

[0023] When the second date is in the first reference week, determining the first monthly calendar as the reference monthly calendar, and displaying all dates of the first reference week on the first monthly calendar;

[0024] Alternatively, when the first date is in the second reference week, the second monthly calendar is determined as the reference monthly calendar, and all dates of the second reference week are displayed in the second monthly calendar;

[0025] Alternatively, when the first date is not in the second reference week and the second date is not in the first reference week, the first calendar month and the second calendar month are determined as the reference calendar month.

[0026] According to some embodiments of the present invention, after identifying each of the target dates in the target view, the method further comprises:

[0027] When the remaining target week blocks are from the same reference calendar, displaying the month information of the first calendar on the first date;

[0028] When the remaining target week blocks come from the first and second calendars, the month information of the first calendar is displayed in the first date, and the month information of the second calendar is displayed in the second date. In the target view, each target date corresponding to the first calendar is marked according to a preset first style box, and each target date corresponding to the second calendar is marked according to a preset second style box.

[0029] According to some embodiments of the present invention, after identifying each of the target dates in the target view, the method further comprises:

[0030] When it is detected that the second option switches from the first source demand to the second source demand, the target date is determined as a candidate date, a new target date is determined based on the second source demand, and the candidate date determined as the new target date is determined as a composite date;

[0031] A new target week array is determined based on the candidate dates and the new target date, and a new target view is rendered and displayed based on the new target week array, wherein display styles of the composite date, the new target date, and the candidate date are different from each other.

[0032] According to some embodiments of the present invention, determining a new target week array based on the candidate date and the new target date includes:

[0033] determining the new target date other than the composite date as the added date;

[0034] Determine the week number of the newly added date based on the reference monthly calendar, and determine the target week block in which the newly added date is located as the newly added week block;

[0035] When the newly added week block is located in the target week array and the position of the newly added date determined based on the week sequence number is not occupied, inserting the newly added date into the newly added week block;

[0036] When the position of any of the newly added dates in the newly added weekly block is occupied by any of the target dates, the newly added weekly block is restored to the reference weekly block and the adjacent weekly block before traversal, and the reference weekly block and the adjacent weekly block are used to replace the newly added weekly block in the target weekly array.

[0037] In a second aspect, an embodiment of the present invention provides a dynamic display device for registration date, comprising at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor so that the at least one control processor can execute the dynamic display method for registration date as described in the first aspect above.

[0038] In a third aspect, an embodiment of the present invention provides an electronic device comprising the dynamic display device for registration date as described in the second aspect above.

[0039] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the method for dynamically displaying the registration date as described in the first aspect above.

[0040] The method for dynamically displaying registration dates according to an embodiment of the present invention has at least the following beneficial effects: based on the target department information obtained from the registration interface, multiple target dates for registration are determined, and at least one reference calendar is generated, wherein the reference calendar corresponds to the month in which the target date is located; each of the reference calendars is split into initial week blocks in units of weeks, and the initial week block in which the target date is located is determined as the target week block; based on any of the target week blocks, the week number of each of the target dates is determined, the first week number is determined as the first sequence number, and the last week number is determined as the last sequence number. The serial number is determined to be the second serial number; the target week blocks are traversed one by one in order, and if the second serial number of the reference week block currently traversed is less than the first serial number of the adjacent week block at the next position, the target date of the adjacent week block is inserted into the reference week block based on the corresponding week serial number, the adjacent week block is deleted, and the second serial number of the reference week block is updated; all the remaining target week blocks are arranged into a target week array based on the format of the reference calendar, and a target view is rendered and displayed based on the target week array, and each target date is identified in the target view. According to the technical solution of the embodiment of the present invention, the calendar can be split into weeks based on the patient's registration needs, and the target week blocks including the target date can be dynamically determined, which flexibly reduces the display range of the calendar; the two target week blocks that can be merged are merged, and the display of invalid dates between the two target week blocks is omitted, further reducing the size of the target week array, and a target view that can view all target dates can be dynamically constructed according to the patient's registration needs, thereby improving the patient experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 This is a schematic diagram of the principle of a method for dynamically displaying registration dates provided by one embodiment of the present invention;

[0042] Figure 2 is a flow chart of a method for dynamically displaying registration dates provided by another embodiment of the present invention;

[0043] Figure 3 This is a schematic diagram of changing the target view after changing the source requirement provided by another embodiment of the present invention;

[0044] Figure 4 This is a complete flow chart of a method for dynamically displaying registration dates provided by another embodiment of the present invention;

[0045] Figure 5 It is a structural diagram of a dynamic display device for registration date provided by another embodiment of the present invention. DETAILED DESCRIPTION

[0046] The following describes embodiments of the present invention in detail. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended only to explain the present invention and are not to be construed as limiting the present invention.

[0047] In the description of the present invention, it should be understood that descriptions involving orientations, such as up, down, front, back, left, right, etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, they cannot be understood as limitations on the present invention.

[0048] In the description of the present invention, "several" means one or more, "many" means more than two, "greater than," "less than," and "exceed" are understood to exclude the number itself, while "above," "below," and "within" are understood to include the number itself. The use of "first" and "second" in the description is solely for the purpose of distinguishing technical features and should not be construed as indicating or implying relative importance, implicitly specifying the number of the indicated technical features, or implicitly specifying the order of the indicated technical features.

[0049] In the description of the present invention, unless otherwise clearly defined, terms such as setting, installing, and connecting should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in the present invention based on the specific content of the technical solution.

[0050] An embodiment of the present invention provides a method, apparatus, device, and storage medium for dynamically displaying registration dates, wherein the method for dynamically displaying registration dates includes: determining multiple target dates for registration based on target department information obtained from a registration interface, generating at least one reference calendar, wherein the reference calendar corresponds to the month in which the target date is located; splitting each of the reference calendars into initial week blocks in units of weeks, and determining the initial week block in which the target date is located as the target week block; determining the week number of each of the target dates based on any of the target week blocks, and determining the first week number as the first number , determine the last of the week numbers as the second number; traverse the target week blocks one by one in order, if the second number of the reference week block currently traversed is less than the first number of the adjacent week block at the next position, insert the target date of the adjacent week block into the reference week block based on the corresponding week number, delete the adjacent week block, and update the second number of the reference week block; arrange all the remaining target week blocks into a target week array based on the format of the reference calendar, render and display the target view based on the target week array, and identify each target date in the target view. According to the technical solution of the embodiment of the present invention, the calendar can be split into weeks based on the patient's registration needs, and the target week blocks including the target date can be dynamically determined, which flexibly reduces the display range of the calendar; the two target week blocks that can be merged are merged, and the display of invalid dates between the two target week blocks is omitted, further reducing the size of the target week array, and a target view that can view all target dates can be dynamically constructed according to the patient's registration needs, thereby improving the patient experience.

[0051] The following is based on the Figure 1 The principle schematic diagram shown further illustrates the technical solution of the embodiment of the present invention.

[0052] Reference Figure 2 , Figure 2 A flowchart of a method for dynamically displaying a registration date provided by an embodiment of the present invention includes but is not limited to the following steps:

[0053] S10, determining multiple target dates for registration based on the target department information obtained from the registration interface, and generating at least one reference calendar, wherein the reference calendar corresponds to the month in which the target date falls;

[0054] S20, splitting each reference calendar into initial weekly blocks in units of weeks, and determining the initial weekly block where the target date is located as the target weekly block;

[0055] S30, based on any target week block, determining the week number of each target date, determining the first week number as the first number, and determining the last week number as the second number;

[0056] S40, traversing the target weekly blocks one by one in sequence, and if the second serial number of the currently traversed reference weekly block is smaller than the first serial number of the next adjacent weekly block, inserting the target date of the adjacent weekly block into the reference weekly block based on the corresponding weekly serial number, deleting the adjacent weekly block, and updating the second serial number of the reference weekly block;

[0057] S50 , arranging all remaining target weeks into a target week array based on a reference calendar format, rendering and displaying a target view based on the target week array, and identifying each target date in the target view.

[0058] It should be noted that the technical solution of this embodiment can be applied to any smart terminal, such as a self-service registration terminal deployed in a hospital, a patient's mobile terminal, etc., which can be connected to the hospital system for registration. Figure 1 The patient terminal 10 shown is provided for schematic illustration.

[0059] It should be noted that this embodiment only obtains the target department information in the registration interface. After the patient selects the specific department they need to visit, the target department information can be selected as an option, or it can be determined by using the symptom description information identified by the artificial intelligence model in the relevant technology. No further restrictions are made here. It is sufficient to be able to obtain the target department information in the registration interface. This embodiment determines the target date for registration based on the number source corresponding to the target department information. The date that is open for registration but no number source is available is not determined as the target date. The earliest target date is the current date.

[0060] For example, Figure 1 As shown, the current date is September 20th. When determining the target date, only the appointments after September 20th will be considered. For example, if there is no doctor on duty on September 23rd, it will not be determined as the target date because there are no appointments available; if the appointments on September 24th are fully booked, it will not be determined as the target date because there are no appointments available.

[0061] It should be noted that the target dates can be distributed within one month or two consecutive months. Hospital registration is different from other appointment scenarios. The hospital scheduling cycle usually does not exceed one month. Therefore, this embodiment only includes one reference calendar and two reference calendar scenarios. The details will not be repeated later. The reference calendar can be generated based on common calendar components. The calendar construction technology will not be described in detail here.

[0062] For example, Figure 1As shown, when the determined target dates include September 20-22 and September 30, the reference calendar 30 is the calendar for September. When the target dates further include October 1-2 and October 14-16, the reference calendar 30 further includes the calendar for October. As long as any target date is included, the calendar for that month can be determined as the reference calendar.

[0063] It should be noted that after determining the reference calendar, if each target date is displayed directly in the reference calendar, the content to be displayed in the target view includes at least the complete reference calendars. Due to the limitation of the display area of ​​the registration interface, it is difficult to ensure that all target dates can be displayed, resulting in the patient needing to perform operations such as turning pages or sliding. Dates other than the target date have no display value to the patient. If only the target date is filtered out for display, the readability of the target view is poor. Therefore, this embodiment needs to reduce the content that does not affect the registration operation while retaining the calendar format, so as to fully display all target dates within the limited display range of the registration interface. Based on this, this embodiment disassembles the reference calendar into weeks. Each reference calendar can be split into multiple initial week blocks. The initial week blocks including the target date are removed as target week blocks, and the initial week blocks that do not include the target date are discarded, thereby reducing unnecessary displayed dates.

[0064] It is worth noting that the splitting of the initial weekly blocks in this embodiment is based on the reference month. The reference month of this embodiment does not display the dates of other months. Therefore, in the case of two reference months, it is very likely that the last initial weekly block of the previous month and the first initial weekly block of the next month correspond to the same week. The initial weekly blocks of this embodiment only display the dates of the current month. Therefore, the aforementioned two initial weekly blocks can be retained, and whether they are determined as target weekly blocks can be determined based on whether there is a target date. On the basis of step S30, if the aforementioned two initial weekly blocks are both determined to be target weekly blocks, they will inevitably be fused in step S30. The same week being divided into multiple target weekly blocks will not lead to an increase in displayed content under the fusion mechanism of step S30.

[0065] For example, Figure 1 As shown, taking September as an example in the reference calendar 30, if the target dates include September 20-22 and September 30, each week corresponds to an initial week block, and the target week block includes the first week block 31 where September 20-22 is located and the second week block 32 where September 30 is located; further, if the reference calendar 30 further includes October, although September 30 and October 1-2 are in the same week, the target week block corresponding to October 1-2 is the third week block 33, and the initial week block corresponding to October 3-9 is discarded because it does not include the target date, and October 14-16 corresponds to the fourth week block 34.

[0066] It should be noted that after determining multiple target week blocks, this embodiment determines the week number of each target date. For example, in the reference calendar, the first day of each week is usually Sunday. The week number corresponding to Sunday is set to 1, Monday is set to 2, and so on.

[0067] It should be noted that after determining the week number of each target date, this embodiment determines the first week number as the first week number and the last one as the second week number. Each target week block will have a date with the same number, for example, there is a Monday and Tuesday every week, and they are aligned in the same order in the monthly calendar. The number of days in each week is the same, and the value range of the first and second numbers is [1,7]. On this basis, this embodiment traverses the target week blocks one by one, determines the current traversed week block as the reference week block, and determines the next one as the adjacent week block. When the second number of the reference week block is less than the first number of the adjacent week block, it can be determined that the last target date of the reference week block is before the first target date of the adjacent week block. Even if there are other dates between the two, they are not target dates. Therefore, not displaying the relevant dates will not affect the patient experience. Based on this, this embodiment merges the qualified reference week blocks and adjacent week blocks into one, so that the target week array for subsequent construction of the target view is reduced by one row. On the basis of only selecting the target week blocks with target dates to reduce the displayed content, the qualified target week blocks are further merged to further reduce the displayed content, ensuring that all target dates can be displayed without turning pages in the registration interface.

[0068] It is worth noting that after completing the traversal of an adjacent weekly block, you can continue to traverse the next adjacent weekly block until the second serial number of the reference weekly block is no longer greater than the first serial number position of the adjacent weekly block. Therefore, this embodiment can merge up to 7 weekly blocks, which can provide a fusion mechanism to reduce invalid display content.

[0069] It is worth noting that when inserting the target date of the adjacent weekly block into the reference weekly block, in order to avoid discontinuous date display, this embodiment replaces all dates after the target date corresponding to the first serial number of the adjacent weekly block into the reference weekly block, thereby realizing the fusion of the two target weekly blocks.

[0070] For example, Figure 1As shown, taking the target weekly block including the first weekly block 31, the second weekly block 32, the third weekly block 33 and the fourth weekly block 34 as an example, the first weekly block 31 is the first reference weekly block traversed, with the first sequence number being 2 and the second sequence number being 4. The next adjacent weekly block traversed is the second weekly block 32. The second weekly block 32 has only one target date (September 30), so the first sequence number and the second sequence number are both 5. The second sequence number of the first weekly block 31 is less than the first sequence number of the second weekly block 32 (4<5), so the second weekly block 32 is traversed. The target date of block 32, September 30th, is inserted into the fifth position of block 31 of the first week. The resulting dates for block 31 of the first week are {19, 20, 21, 22, 30}. Of course, the dates with week numbers 6 and 7 of block 31 of the first week are not displayed at this time to avoid misleading the patient. For example, if {19, 20, 21, 22, 30, 24, 25} is displayed, it is easy for the patient to mistakenly believe that 30 is a system failure. Therefore, in this embodiment, all dates after the first number in the adjacent week blocks are inserted into the reference week block. For example, if the target date of block 31 of the first week is the 19th, and the target dates of block 32 of the second week are the 28th and 29th, the dates of block 31 of the first week after fusion are {19, 20, 28, 29, 30}. Although the 30th is not the target date, it will be inserted into block 31 of the first week following the target date of block 32 of the second week.

[0071] For example, continue to refer to the above example. After completing the operation of the second week block 32, continue to traverse to the third week block 33, whose target dates are the 1st and the 2nd, and the corresponding first sequence number is 6, and the second sequence number is 7. The second sequence number of the first week block 31 after update is 5, which still meets the above conditions. The two target dates of the third week block 33 are inserted into the first week block 31, so that the obtained first week block 31 is finally {19, 20, 21, 22, 30, 1, 2}. Since the updated second sequence number reaches 7, the traversal is stopped, and the next one determined as the reference week block is the fourth week block 34. If the second sequence number of the first week block 31 after update is 6, the first sequence number of the fourth week block 34 can also be compared based on the first week block 31, and so on.

[0072] It should be noted that if there is only one target week block after the merger, the target week block can be directly determined as the target week array. If there are multiple target week blocks after the merger, they can be arranged from top to bottom according to the format of the reference calendar to obtain the target week array. After obtaining the target week array, the target view can be rendered and displayed in the patient terminal.

[0073] like Figure 1As shown, the merged target week array 40 includes the first week block 31 and the fourth week block 34. The target view is rendered based on the target week array 40, and is displayed from Sunday to Saturday according to the format of the reference calendar. The target date and other dates are displayed in different styles, such as by assigning different background colors and using different font weights in the corresponding table cells.

[0074] In addition, in one embodiment, referring to Figure 4 In step S10, multiple target dates for registration are determined based on the target department information obtained from the registration interface, specifically including but not limited to the following steps:

[0075] S111, constructing a first option and a second option in the registration interface, wherein the first option includes multiple optional department information, and the second option includes multiple optional number source requirements, and the optional number source requirements are used to indicate the consultation time or the doctor to be consulted;

[0076] S112, obtaining the target department information selected in the first option, determining the registration dates of the departments that have opened registration based on the target department information, and determining the optional number sources corresponding to the registration dates of each department;

[0077] S113, obtaining the first source requirement selected in the second option, and screening the target source from multiple optional sources based on the first source requirement;

[0078] S114, determining the department registration date corresponding to the target number source as the target date.

[0079] It should be noted that this embodiment displays the first option and the second option in the registration interface of the patient terminal. The first option is filled with optional department information, and the second option is filled with optional number source requirements. The target date is dynamically determined through the patient's visual operation.

[0080] For example, Figure 1 As shown, the patient terminal 10 displays the first option 21, which displays various departments that can be registered. Taking the selected target department information as surgery as an example, the second option 22 pops up, and various optional number source requirements are displayed in the second option 22. The optional number source requirement can be to select a doctor. After clicking, the numbers of various surgical doctors can be obtained from the hospital system as optional number sources; the optional number source requirement can also be the consultation time. For example, when choosing a consultation in the morning, the date with optional number sources in the morning is determined as the target date, and so on.

[0081] It should be noted that after determining the target department information, the registration date for the department with available appointments can be determined based on common scheduling information. For example, if the schedule is typically two weeks, the department registration date can be calculated two weeks from the current date. Of course, dates with no doctors available will not be determined as department registration dates because there are no available appointments. After determining the department registration date, determining the available appointment sources is a technique well known to those skilled in the art.

[0082] It should be noted that each optional number source records the corresponding doctor and consultation time. Therefore, based on the patient's first number source requirement selected in the second option, the target number source can be screened out from the optional number sources, and the department registration date corresponding to the target number source can be determined as the target date, thereby dynamically screening the target date according to the patient's choice.

[0083] For example, the first number source demand is for consultation in the morning, and the optional number source with consultation time between 8:00-12:00 is determined as the target number source, and so on.

[0084] In addition, in one embodiment, referring to Figure 4 In step S10, at least one reference calendar is generated, including but not limited to the following steps:

[0085] S121, determining the first target date as the first date, and determining the last target date as the second date;

[0086] S122, when the first date and the second date correspond to the same month, inputting the first date into a preset calendar component to generate a first calendar, and determining the first calendar as a reference calendar;

[0087] S123, when the first date and the second date correspond to different months, input the first date into the calendar component to generate a first calendar, input the second date into the calendar component to generate a second calendar, and determine at least one reference calendar based on the first calendar and the second calendar.

[0088] It should be noted that after determining the target dates, this embodiment sets the first target date as the first date and the last target date as the second date. If the first and second dates fall in the same month, the reference calendar only has one month. Inputting the first date into the calendar component generates the first calendar, which serves as the reference calendar. The reference calendar can be generated using a common calendar component, such as the common FullCalendar component, which generates a calendar view by inputting a year and month. The specific principles will not be repeated here.

[0089] It should be noted that when the first date and the second date are in different months, since the second date is the last target date, it must be in the second month. The first date and the second date can be input into the calendar component respectively to obtain the corresponding reference calendar.

[0090] In addition, in one embodiment, referring to Figure 4 In step S123, at least one reference calendar is determined based on the first calendar and the second calendar, including but not limited to the following steps:

[0091] S1231, determining the last week of the first calendar month as the first reference week, and determining the first week of the second calendar month as the second reference week;

[0092] S1232, when the second date is in the first reference week, determining the first monthly calendar as the reference monthly calendar, and displaying all dates of the first reference week in the first monthly calendar;

[0093] S1233, when the first date is in the second reference week, determining the second monthly calendar as the reference monthly calendar, and displaying all dates of the second reference week in the second monthly calendar;

[0094] S1234: When the first date is not in the second reference week and the second date is not in the first reference week, the first and second monthly calendars are determined as reference monthly calendars.

[0095] It should be noted that, according to the description of the above embodiment, the first and second calendars only display the dates of the current month. When determining two reference calendars, this embodiment determines the last week of the first calendar as the first reference week, and the first week of the second calendar as the second reference week. According to the description of the above embodiment, the first and second reference weeks can be the same week, but are split into two initial week blocks due to the different corresponding dates. If only one week in the first or second calendar has a target date, if the entire calendar is determined as the reference calendar, multiple initial week blocks will be generated, resulting in unnecessary calculations. For example, if the second date falls in the first reference week, the second date is the last target date, and there are no other target dates after the second date, only the second reference week of the second calendar will be determined as the target reference week. After the second date is integrated into the first calendar, not determining the second calendar as the reference calendar will not affect the display of the target date. Based on this, this embodiment displays all dates of the first reference week on the first calendar to cover the second date, and only determines the first calendar as the target calendar. This can omit the second calendar, thereby reducing multiple initial week blocks and unnecessary calculations. The same applies if the first date falls in the second reference week.

[0096] For example, Figure 1As shown, if the second date is October 1st, then the second date is in the first reference week. In this case, October 1st and October 2nd will be displayed in September. There is no need to determine October as the reference calendar month. Instead, the first calendar month corresponding to September can be split into multiple initial week blocks. Similarly, if the first date is September 30th, which is in the second reference week, the second calendar month corresponding to October will be determined as the reference calendar month. The corresponding dates in September will be displayed in the first week of October without determining September as the reference calendar month.

[0097] In addition, in one embodiment, referring to Figure 4 After executing step S50, the process further includes but is not limited to the following steps:

[0098] S61, when the remaining multiple target week blocks are from the same reference calendar, displaying the month information of the first calendar on the first date;

[0099] S62, when the remaining target week blocks come from the first and second monthly calendars, the month information of the first calendar is displayed in the first date, and the month information of the second calendar is displayed in the second date. In the target view, each target date corresponding to the first month is marked according to a preset first style box, and each target date corresponding to the second calendar is marked according to a preset second style box.

[0100] It should be noted that after the merging of multiple target week blocks is completed according to the method of step S30, when the remaining multiple target week blocks come from the same reference calendar, it is only necessary to display the month information of the first calendar on the first date to clearly indicate that the current target week array is displaying the content of the same month, such as Figure 1 As shown, if the reference calendar corresponding to the target week array is September, September 20th will be displayed in the target date corresponding to the 20th, and the remaining dates do not need to display the month.

[0101] It should be noted that when a merge operation is performed on a target week segment, it may include dates from two reference calendars. To improve display accuracy, this embodiment utilizes the fact that the first and second dates necessarily belong to different reference calendars, displaying the month information of the first calendar on the first date and the month information of the second calendar on the second date. Furthermore, to provide a more intuitive visual distinction, this embodiment pre-sets a first style frame and a second style frame. The first and second style frames have different styles, and their shapes are dynamically adjusted based on the distribution of the target dates. These frames are automatically generated based on the location of the target date in the target week array.

[0102] For example, Figure 1As shown, the target week blocks include a first week block 31 and a fourth week block 34, so September is displayed at the target date 20th of the first week block 31, October is displayed at the 16th of the fourth week block 34, and the solid line frame is used as the first style frame to select the 20th, 21st, 22nd and 30th days, and the dotted line frame is used as the second style frame to select the 1st, 2nd, 13th to 16th days.

[0103] In addition, in one embodiment, referring to Figure 4 After executing step S50, the process further includes but is not limited to the following steps:

[0104] S71, when it is detected that the second option switches from the first source demand to the second source demand, the target date is determined as a candidate date, a new target date is determined based on the second source demand, and the candidate date determined as the new target date is determined as a composite date;

[0105] S72, determining a new target week array based on the candidate dates and the new target date, rendering and displaying a new target view based on the new target week array, wherein the display styles of the composite date, the new target date, and the candidate date are different from each other.

[0106] It should be noted that, according to the description at step S10, Figure 1 As shown, the patient terminal can select the number source demand through the second option 22 on the registration interface, and when there is no target date required by the patient in the target view generated based on the first number source demand, for example, the patient wants to see a doctor on September 23, but Figure 1 The target date of the target week array 40 shown does not include September 23, so the patient can further change the number source demand in the second option 22, for example, switching from the first number source demand of morning visit to the second number source demand of afternoon visit. By switching the number source demand, the target date in the target view is dynamically adjusted to determine the target date that meets the patient's needs.

[0107] It should be noted that after switching the number source demand, this embodiment does not re-execute the steps of the above embodiment to generate another target view. Instead, on the basis of the target view obtained based on the first number source demand, the new target date determined based on the second number source is superimposed, and the target dates obtained by the two number source demands are displayed in the target view at the same time. This can provide patients with a more complete date display visually, without the need to frequently switch between different number source demands for selection.

[0108] It should be noted that the same target date or different target dates may be obtained based on different source requirements. Although the patient has switched to the second source requirement, the second source requirement may be switched only for comparison with the first source requirement. Therefore, this embodiment determines the target date obtained based on the first source requirement as the candidate date, and determines the target date corresponding to the second source requirement as the new target date. If the new target date and the candidate date are the same date, the date is determined as a composite date.

[0109] It should be noted that the method of determining the new target week array based on the candidate date and the new target date in this embodiment can refer to the description of the above embodiment. The candidate date and the new target date can be used as the target date in the above embodiment to determine the target week blocks, and no further details will be given here.

[0110] For example, Figure 3 As shown, the new target dates are September 23-25, September 28-30, October 1-2, and October 6-8. September 30, October 1, and October 2 are also included. Figure 1 The target date shown is therefore determined to be a composite date, Figure 1 The remaining target dates (September 20-22, October 13-16) are determined as candidate dates, September 23-25, September 28-29, October 6-8 are the new target dates, and the target week array 40 is obtained as a reference. Figure 3 shown.

[0111] It should be noted that after obtaining the new target week array, this embodiment displays the composite date, new target date and candidate date in different styles in the new target view. Patients can directly distinguish different date types visually, thereby improving the patient experience.

[0112] For example, Figure 3 As shown, in the target week array 40 , candidate dates are displayed in italics, new target dates are displayed in bold, and composite dates are displayed in special fonts. The specific style can be selected according to actual needs and is not limited here.

[0113] In addition, in one embodiment, referring to Figure 4 In step S72, a new target week array is determined based on the candidate date and the new target date, including but not limited to the following steps:

[0114] S721, the new target date other than the composite date is determined as the newly added date;

[0115] S722, determining the week number of the newly added date based on the reference monthly calendar, and determining the target week block where the newly added date is located as the newly added week block;

[0116] S723, when the newly added week block is located in the target week array and the position of the newly added date determined based on the week number is not occupied, the newly added date is inserted into the newly added week block;

[0117] S724, when the position of any newly added date in the newly added weekly block is occupied by any target date, the newly added weekly block is restored to the reference weekly block and adjacent weekly block before traversal, and the reference weekly block and adjacent weekly block are used to replace the newly added weekly block in the target weekly array.

[0118] It should be noted that according to the definition of the above embodiment, the composite date is obtained based on the first source demand, so the composite date will inevitably be displayed in the target week array obtained initially. New target dates other than the composite date are added dates, which may not be displayed in the target week array. If the reference calendar is re-disassembled and merged based on each candidate date, composite date, and added date, it will consume a long calculation time, which will be reflected as a lag on the patient terminal. However, the candidate date and composite date are already displayed in the target week array, and only the added date needs to be added.

[0119] It should be noted that this embodiment performs fusion of multiple target week blocks in step S30, so the newly added date is likely to be replaced during the fusion process. This embodiment first determines the week number of the newly added date, and in the initial week blocks obtained by splitting the reference calendar, determines the target week block where the newly added date is located as the newly added week block. If the newly added week block is not in the target week array, the newly added week block is inserted into the target week array, for example Figure 3 As shown, the newly added week block corresponding to October 3-9 is inserted into the target week array 40. If the newly added week block is located in the target week array and the week number of the newly added date is not occupied by a candidate date or a composite date, the date corresponding to the week number is an invalid date, and the newly added date can be directly inserted into the corresponding position.

[0120] It should be noted that when the newly added date is occupied by any target date, it can be determined that the newly added block has performed the fusion operation in step S30, resulting in the newly added date being fused when the target weekly block was determined last time. This embodiment restores the newly added weekly block to the reference weekly block and the adjacent weekly block of the convenience note. Since the newly added date is added, the second serial number of the reference weekly block must change, which makes it impossible for the reference weekly block to be fused with the adjacent weekly block. The reference weekly block and the adjacent block replace the newly added weekly block in the target array, thereby displaying two complete weekly blocks.

[0121] For example, Figure 3As shown, the first week block in the target week array is merged. After September 23-25 ​​is determined to be the newly added date, the corresponding position in the first week block is occupied. Therefore, the first week block is restored to the first week block, the second week block, and the third week block before fusion. The above three week blocks are inserted into the target week array respectively to ensure that every newly added date, compound date, and candidate date can be displayed.

[0122] like Figure 5 As shown, Figure 5 This is a structural diagram of a dynamic display device for registration date provided by an embodiment of the present invention. The present invention also provides a dynamic display device for registration date, comprising:

[0123] The processor 401 may be implemented as a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is configured to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0124] Memory 402 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). Memory 402 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in memory 402 and is called by processor 401 to execute the method for dynamically displaying the registration date in the embodiments of this application.

[0125] Input / output interface 403, used to implement information input and output;

[0126] Communication interface 404, used to implement communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WiFi, Bluetooth, etc.);

[0127] Bus 405 , which transmits information between various components of the device (e.g., processor 401 , memory 402 , input / output interface 403 , and communication interface 404 );

[0128] The processor 401 , the memory 402 , the input / output interface 403 and the communication interface 404 are connected to each other in communication within the device via a bus 405 .

[0129] An embodiment of the present application also provides an electronic device, comprising the dynamic display device for registration date as described above.

[0130] An embodiment of the present application also provides a storage medium, which is a computer-readable storage medium and stores a computer program. When the computer program is executed by a processor, the above-mentioned dynamic display method of the registration date is implemented.

[0131] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory optionally includes a memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of the above-mentioned networks include but are not limited to the Internet, an intranet, a local area network, a mobile communication network and a combination thereof. The device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and are located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment.

[0132] Those skilled in the art will appreciate that all or some of the steps and systems disclosed above can be implemented as software, firmware, hardware, or any suitable combination thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is well known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disks (DVDs) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0133] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above implementation. Those skilled in the art can also make various equivalent modifications or substitutions under the shared conditions that do not violate the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A method for dynamically displaying a registration date, characterized in that: The method comprises: Determine multiple target dates for registration based on the target department information obtained from the registration interface, and generate at least one reference calendar, wherein the reference calendar corresponds to the month in which the target date falls; Splitting each reference calendar into initial weekly blocks in units of weeks, and determining the initial weekly block where the target date is located as the target weekly block; Based on any of the target week blocks, determine the week numbers of the target dates, determine the first week number as the first number, and determine the last week number as the second number; Traversing the target weekly blocks one by one in sequence, if the second serial number of the currently traversed reference weekly block is less than the first serial number of the next adjacent weekly block, inserting the target date of the adjacent weekly block into the reference weekly block based on the corresponding weekly serial number, deleting the adjacent weekly block, and updating the second serial number of the reference weekly block, wherein the non-target date following the target date corresponding to the first serial number of the adjacent weekly block is synchronously inserted into the reference weekly block; All the remaining target week blocks are arranged into a target week array based on the format of the reference calendar, a target view is rendered and displayed based on the target week array, and each target date is identified in the target view.

2. The method for dynamically displaying the registration date according to claim 1, characterized in that: Based on the target department information obtained from the registration interface, multiple target dates for registration are determined, including: Constructing a first option and a second option in the registration interface, wherein the first option includes multiple optional department information, and the second option includes multiple optional number source requirements, and the optional number source requirements are used to indicate the consultation time or the consultation doctor; Obtaining the target department information selected in the first option, determining the department registration dates that are open for registration based on the target department information, and determining the selectable number sources corresponding to each of the department registration dates; Obtaining the first signal source requirement selected in the second option, and screening a target signal source from the plurality of optional signal sources based on the first signal source requirement; The department registration date corresponding to the target number source is determined as the target date.

3. The method for dynamically displaying the registration date according to claim 2, characterized in that: Generate at least one reference monthly calendar, including: determining the first of said target dates as a first date and the last of said target dates as a second date; When the first date and the second date respectively correspond to the same month, the first date is input into a preset calendar component to generate a first calendar, and the first calendar is determined as the reference calendar; Alternatively, when the first date and the second date correspond to different months, the first date is input into the calendar component to generate the first calendar, the second date is input into the calendar component to generate the second calendar, and at least one reference calendar is determined based on the first calendar and the second calendar.

4. The method for dynamically displaying the registration date according to claim 3, characterized in that: Determining at least one reference monthly calendar based on the first monthly calendar and the second monthly calendar includes: Determine the last week of the first calendar month as a first reference week, and determine the first week of the second calendar month as a second reference week; When the second date is in the first reference week, determining the first monthly calendar as the reference monthly calendar, and displaying all dates of the first reference week on the first monthly calendar; Alternatively, when the first date is in the second reference week, the second monthly calendar is determined as the reference monthly calendar, and all dates of the second reference week are displayed in the second monthly calendar; Alternatively, when the first date is not in the second reference week and the second date is not in the first reference week, the first calendar month and the second calendar month are determined as the reference calendar month.

5. The method for dynamically displaying the registration date according to claim 3, characterized in that: After identifying each of the target dates in the target view, the method further includes: When the remaining target week blocks are from the same reference calendar, displaying the month information of the first calendar on the first date; When the remaining target week blocks come from the first and second calendars, the month information of the first calendar is displayed in the first date, and the month information of the second calendar is displayed in the second date. In the target view, each target date corresponding to the first calendar is marked according to a preset first style box, and each target date corresponding to the second calendar is marked according to a preset second style box.

6. The method for dynamically displaying the registration date according to claim 2, characterized in that: After identifying each of the target dates in the target view, the method further includes: When it is detected that the second option switches from the first source demand to the second source demand, the target date is determined as a candidate date, a new target date is determined based on the second source demand, and the candidate date determined as the new target date is determined as a composite date; A new target week array is determined based on the candidate dates and the new target date, and a new target view is rendered and displayed based on the new target week array, wherein display styles of the composite date, the new target date, and the candidate date are different from each other.

7. The method for dynamically displaying the registration date according to claim 6, characterized in that: Determining a new target week array based on the candidate date and the new target date includes: determining the new target date other than the composite date as the added date; Determine the week number of the newly added date based on the reference monthly calendar, and determine the target week block in which the newly added date is located as the newly added week block; When the newly added week block is located in the target week array and the position of the newly added date determined based on the week sequence number is not occupied, inserting the newly added date into the newly added week block; When the position of any of the newly added dates in the newly added weekly block is occupied by any of the target dates, the newly added weekly block is restored to the reference weekly block and the adjacent weekly block before traversal, and the reference weekly block and the adjacent weekly block are used to replace the newly added weekly block in the target weekly array.

8. A dynamic display device for registration date, characterized in that: It includes at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to execute the dynamic display method of the registration date as described in any one of claims 1 to 7.

9. An electronic device, characterized in that: Including the dynamic display device for registration date as described in claim 8.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the dynamic display method of the registration date according to any one of claims 1 to 7.

Images