locked
Importing and updating records RRS feed

  • Question

  • Hi,

    I am trying to use CRM as a patient mangagement system to track calls, appointment followup, etc.  Though it is not "sales" the need is to have followup and manage various parameters.  I have looked at data import but want to see if I have the issues correctly.

    1. You can import records from another database which in this case is SQL Anywhere.

    2. In this case, the record fields in the import database change so therefore the old records need to be updated and any new one's added.

    3. I have successfully imported but am confused on updating records.  It appears that you can not do this easily.  You can look for duplicates but in this case this would consist of manually checking a couple thousand recoreds each time there is an import.

    4. It appears that Scribe software allows you do the type of updates I am talking about.

    Is the above correct?

    Thanks.

    David

    Friday, May 13, 2011 5:42 PM

Answers

  • Hi,

    Scribe is quite a powerful software not only for importing data, but also for keeping integration between two data sources.

    For importing, what it can do is to queue the whole importing process to ensure that relationships are imported in a "streamlined" manner. So it makes sure for example, that when you're importing accounts, it will create all parent accounts and then add the accounts that are "children" of those parent accounts. If you use another method of importing data, and you don't take parent account and child accounts into consideration, during the import, if a children account can't find its parent account in the system (say, it haven't been created yet), the import would fail.

    Also, if you want to use the import feature of Dynamics CRM 2011 (I assume you using Dynamics CRM 2011) you must import data from files. For example, Excel 2003 XML files, or comma separated value files (CSV). Scribe on the other hand allow you to use connectors that can plug straight into the data source, be it a "generic" SQL database, or a Dynamics CRM 4 database, SAP, etc.

    When importing data with the Dynamics CRM data import function, it allows you to set what fields would consider the records to be duplicate. For instance, when importing patients you might want to say that FULL NAME (a combination of Name and Last Name) is what ensures that they're duplicate. However since it is often the case that people can bear the same name, you might want to look into another field like National ID number or Payroll number, or Patient Record Number. Finally, you can choose if you want to allow duplicates to be imported based on the duplicate detection rule you set out.

    Depending on the amount of data you have and how often you will have to import data into CRM, Scribe might be an overkill.

    I am not an expert in Scribe but I worked with teams that used it before and if I had to integrate Dynamics with any other product or perform a complex and time-consuming import, Scribe would be the first solution I would look into.

    • Proposed as answer by pmdci Friday, May 13, 2011 6:36 PM
    • Marked as answer by davidkerr Saturday, May 14, 2011 7:19 AM
    Friday, May 13, 2011 6:04 PM
  • Hi David,

     

    I just deliverd a "Patient Management" solution for a clinic, we had similar scenario than you mention. We imported the records using the import templates that CRM provides (you just fill them in with your SQL data). Before importing, we defined our custom duplicate detection rules and enabled them so during import you can select to use duplicate detection and for every record which is considered a duplicate you get a report that tells you which records were not imported and why (which duplicate detection rule they failed). We had rules like "patients with the same memberID or with the same telephone number, etc).

     

    After we imported the data we figured for example, that we forgot about one of the fields (member expiration date), so instead of bulk deleting and re-importing all the patient records, we exported the CRM records to XML and you can mark "export for re-import". Then you fill out the missing fields in Excel and re-import the document, the re-import will update all the existing records with the new value.

    The down side is that from the moment you export the records until the moment you re-import the updated spreadsheet, nobody is allowed to change the records (otherwise update will fail for each updated record).

    • Marked as answer by davidkerr Saturday, May 14, 2011 7:19 AM
    Friday, May 13, 2011 8:38 PM
    Moderator

All replies

  • Hi,

    Scribe is quite a powerful software not only for importing data, but also for keeping integration between two data sources.

    For importing, what it can do is to queue the whole importing process to ensure that relationships are imported in a "streamlined" manner. So it makes sure for example, that when you're importing accounts, it will create all parent accounts and then add the accounts that are "children" of those parent accounts. If you use another method of importing data, and you don't take parent account and child accounts into consideration, during the import, if a children account can't find its parent account in the system (say, it haven't been created yet), the import would fail.

    Also, if you want to use the import feature of Dynamics CRM 2011 (I assume you using Dynamics CRM 2011) you must import data from files. For example, Excel 2003 XML files, or comma separated value files (CSV). Scribe on the other hand allow you to use connectors that can plug straight into the data source, be it a "generic" SQL database, or a Dynamics CRM 4 database, SAP, etc.

    When importing data with the Dynamics CRM data import function, it allows you to set what fields would consider the records to be duplicate. For instance, when importing patients you might want to say that FULL NAME (a combination of Name and Last Name) is what ensures that they're duplicate. However since it is often the case that people can bear the same name, you might want to look into another field like National ID number or Payroll number, or Patient Record Number. Finally, you can choose if you want to allow duplicates to be imported based on the duplicate detection rule you set out.

    Depending on the amount of data you have and how often you will have to import data into CRM, Scribe might be an overkill.

    I am not an expert in Scribe but I worked with teams that used it before and if I had to integrate Dynamics with any other product or perform a complex and time-consuming import, Scribe would be the first solution I would look into.

    • Proposed as answer by pmdci Friday, May 13, 2011 6:36 PM
    • Marked as answer by davidkerr Saturday, May 14, 2011 7:19 AM
    Friday, May 13, 2011 6:04 PM
  • Hi David,

     

    I just deliverd a "Patient Management" solution for a clinic, we had similar scenario than you mention. We imported the records using the import templates that CRM provides (you just fill them in with your SQL data). Before importing, we defined our custom duplicate detection rules and enabled them so during import you can select to use duplicate detection and for every record which is considered a duplicate you get a report that tells you which records were not imported and why (which duplicate detection rule they failed). We had rules like "patients with the same memberID or with the same telephone number, etc).

     

    After we imported the data we figured for example, that we forgot about one of the fields (member expiration date), so instead of bulk deleting and re-importing all the patient records, we exported the CRM records to XML and you can mark "export for re-import". Then you fill out the missing fields in Excel and re-import the document, the re-import will update all the existing records with the new value.

    The down side is that from the moment you export the records until the moment you re-import the updated spreadsheet, nobody is allowed to change the records (otherwise update will fail for each updated record).

    • Marked as answer by davidkerr Saturday, May 14, 2011 7:19 AM
    Friday, May 13, 2011 8:38 PM
    Moderator