# US 10,769,173 B1 · Systems and methods for data migration > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,769,173 B1 - Document ID: US10769173B1 - Status: Granted - Kind: B1 - Application number: 16/506,739 - Filed: 2019-07-09 - Granted: 2020-09-08 - Earliest claimed: 2013-08-21 - Assignees: Allscripts Software, LLC - Applicants: Allscripts Software, LLC - Inventors: George Rizk Mechael; Laurie A. Hart; Angela Hodgetts; Pamela Fleury - Web page: https://patentgrep.com/patent/US10769173B1 ## CPC - G16H 10/60: for patient-specific data, e.g. for electronic patient records - G06F 3/0482: Interaction with lists of selectable items, e.g. menus - G06F 16/214: {Database migration support} - G06F 16/25: Integrating or interfacing systems involving database management systems - G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor - G16H 15/00: ICT specially adapted for medical reports, e.g. generation or transmission thereof - G16H 40/63: for local operation - G06F 3/0488: using a touch-screen or digitiser, e.g. input of commands through traced gestures - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method includes importing legacy data from a legacy application into a new system by storing the legacy data in a database separate from data native to the new system; displaying, to a user via a display screen, an interface configured to allow a user to view both legacy data and data native to the new system; displaying, to the user via a display screen, an interface including information of the legacy data that is associated with a particular patient account, one or more interface elements configured to allow the user to perform limited actions with respect to the particular patient account associated with the information, and a user interface element configured to allow a user to selectively activate the patient account. ## Claims ### Claim 1 A method comprising: (a) importing legacy data from a legacy application into a new system by storing the legacy data in a legacy database separate from data native to the new system; (b) maintaining, at the new system, (i) a first balance for a particular patient account in the legacy database, and (ii) a second balance for the particular patient account in a native database that stores data native to the new system, wherein the first balance in the legacy database and the second balance in the native database are maintained to remain independent of one another; (c) generating an interface configured to allow a user to access both legacy data and data native to the new system the interface including (i) information of the legacy data that is associated with the particular patient account, and (ii) one or more interface elements configured to perform limited actions to be performed with respect to the particular patient account associated with the information; (d) receiving input, via an input device corresponding to engagement of one of the user interface elements configured to perform limited actions with respect to the particular patient account associated with the information; and (e) in response to receiving input corresponding to engagement of one of the user interface elements configured to perform limited actions with respect to the particular patient account associated with the information, automatically updating both the first balance in the legacy database and the second balance in the native database while maintaining the independence of such balances by (i) modifying the first balance in the legacy database causing the first balance to have a first value, and (ii) modifying the second balance in the native database that stores data native to the new system, causing the second balance to have a second value different than the first value. ### Claim 2 (depends on 1) The method of claim 1, wherein the input device comprises a laptop. ### Claim 3 (depends on 1) The method of claim 1, wherein the input device comprises a tablet. ### Claim 4 (depends on 1) The method of claim 1, wherein the input device comprises a phone. ### Claim 5 (depends on 1) The method of claim 1, wherein the input device comprises a computer. ### Claim 6 (depends on 1) The method of claim 1, wherein the input device comprises a touch screen. ### Claim 7 (depends on 1) The method of claim 1, wherein the input device comprises a mouse. ### Claim 8 (depends on 1) The method of claim 1, wherein the input device comprises a keyboard. ### Claim 9 (depends on 1) The method of claim 1, wherein the legacy application comprises an application configured for use in a health care context. ### Claim 10 One or more non-transitory computer readable media containing computer executable instructions configured to perform a method comprising: (a) importing legacy data from a legacy application into a new system by storing the legacy data in a legacy database separate from data native to the new system; (b) independently maintaining, at the new system, (i) a first balance for a particular patient account in the legacy database, and (ii) a second balance for the particular patient account in a native database that stores data native to the new system; (c) generation an interface configured to allow a user to view both legacy data and data native to the new system, the interface including (i) information of the legacy data that is associated with the particular patient account, and (ii) one or more interface elements configured to allow the user to perform limited actions with respect to the particular patient account associated with the information; (d) receiving input corresponding to engagement of one of the user interface elements configured to perform limited actions with respect to the particular patient account associated with the information; and (e) in response to receiving input corresponding to engagement of one of the user interface elements configured to perform limited actions with respect to the particular patient account associated with the information, automatically updating both the first balance in the legacy database and the second balance in the native database while maintaining the independence of such balances by (i) modifying the first balance in the legacy database causing the first balance to have a first value, and (ii) modifying the second balance in the native database that stores data native to the new system causing the second balance to have a second value different than the first value. ### Claim 11 A method comprising: (a) importing legacy data from a legacy application into a new system by storing the legacy data in a legacy database separate from data native to the new system; (b) independently maintaining, at the new system, (i) a first balance for a particular patient account in the legacy database, and (ii) a second balance having a first value for the particular patient account in a native database that stores data native to the new system; (c) generating an interface including (i) information of the legacy data that is associated with the particular patient account, and (ii) one or more interface elements configured to perform limited actions with respect to the particular patient account associated with the information; (d) receiving input corresponding to engagement of one of the user interface elements configured to allow the user to perform limited actions with respect to the particular patient account associated with the information; and (e) in response to receiving the input, automatically updating both the first balance in the legacy database and the second balance in the native database while maintaining the independence of such balances by modifying the first balance and the second balance to cause the second balance to have a second value different than the first value.