| id | title | date | version | lastAuthor | mimeType | links | source | wikigdrive | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
1XAl3AqJTGB3Hb7Cfm_ix2IOxF2hE23GI_ysA3cX8ZJk |
Data Import Overview |
2020-02-27T21:30:32.809Z |
27 |
aquandt |
text/x-markdown |
|
0008bcbb1563384efe0a28ada6f97e9432e65f10 |
This page provides an explanation of terminology related to importing data from an existing system to the {{% system-name %}} system.
Clients replacing an existing EHR with an {{% system-name %}} system undertake what is referred to as data migration. Multiple sets of data may be involved in a data migration, but the migration is a one-time event.
Imports essentially move data from one place to another, can be repeated at regular intervals, and may be an ongoing process. Imports may be part of the migration process, while data migration is considered to be a single event.
An application program interface (API), as utilized by MIE, is a specification that directs how the {{% sys-name %}} system interacts with data that is being imported from another system. CSV APIs have been developed to allow client users to import information into their own system.
Comma separated values (CSV) files are used to transfer data through an API. To simplify, CSV files are simply text files with data fields separated by commas (or another supported character/delimiter) . For more on file formatting standards, see Data Migration File Format Standard.
A number of developer tools have been designed to aide data import efforts. These tools require a developer to operate.