Storing medical record number or date of service

Options
Does anyone have a standard practice for storing a donor's patient record number or date of encounter in the Raiser's Edge?

Comments

  • We don't have a need to do this, but I know there are other threads in the Community regarding storing other ID data in RE (particularly this one about storing a student ID).  An Alias, replacing the SSN field, an Attribute, or as part of a concatenated RE ConstituentID may work for you.  I highly recommend determining what options may work and testing them on a small set of records.  Once you figure out which option works best, you can implement it across the database and remove the other tests.


     
  • We needed to store employee ID numbers.  So on the BIO2, I changed the Birthplace field to Employee I.D. and mapped it in my new employee imports.  Works great!


    Patti Posey

    Stamford Hospital Foundation
  • We changed the SSN field to PID (Patient Identification number).  This works well for us.


    FYI, we use the Alias field to store Student ID for those who are students of the Medical College.  (a smaller group)
  • I haven't seen this listed yet, we actually created a phone type and store ID numbers there.
  • Tevis O'Mahony:

    We changed the SSN field to PID (Patient Identification number).  This works well for us.


    FYI, we use the Alias field to store Student ID for those who are students of the Medical College.  (a smaller group)

    Tevis

    Do you have a policy or procedure for inputting this information and do you store any other medical information such as date of visit?  Many thanks for your help!

    Donna

  • I'm the data analyst for the foundation for a fairly descent sized health system. Our compliance department will not allow us to save anything in our database that could show that a donor had been a patient. I'm wondering if storing a patient ID number and dates of admission might not cause concerns with HIPAA regulations.


    We DO however use the SSN field to store employee ID numbers, since it was determined that we didn't want the responsibility of storing actual SSNs.
  • Two different health organizations I know have two different views:


    1. No info, period.


    2. Patient ID may be used IF AND ONLY IF it carries no clinical data with it; for example, it's a simple number only and doesn't indicate service line, diagnosis, etc., by some sort of special coding or formatting of the patient ID. Dates of service can also be recorded, though very little else with that.


    HIPAA does allow use of certain demographic info for fundraising purposes. Two resources to use to review what is considered "demographic info" are:


    http://www.givinginstitute.org/news/250351/The-HIPAA-Privacy-Rule-What-Fundraisers-Need-to-Know.htm

    http://connect.ahp.org/HigherLogic/System/DownloadDocumentFile.ashx?DocumentFileKey=6b50190e-959c-4454-813e-8f2943c77d44


    My personal opinion, based on reading, discussions, and my experience, has been to lean towards the latter interpretation.


    When used, I've also seen the Patient ID stored in the SSN field, which I think is a brilliant move because it means you can never have the same Patient ID on multiple records. Visit info was limited to the most recent visit and stored as an attribute. I would be very cautious about keeping much in terms of visit info in RE because the quantity of data could grow far too quickly and may not be of much value for fundraising purposes (for example, a lab visit is not generally useful to have in RE).


    Best of luck!
  • Because we have a grateful patient program, we have invested a lot of time in this subject.  We are a public hospital, part of the state university system, and our process has been approved through our hospital's HIPAA compliance officers.  We can download patient lists.  We screen them and upload only those with a specific rating or higher, using Omatic software (ImportOMatic and List Management).  We store the patient ID number in the alias field.  We create actions for each patient visit and store information such as the physician and service area as action attributes.  We've been doing this for over a year.  It is a process to set up, but it seems to be working well.
  • Sue,


    Do you use NXT?  How are you HIPAA compliant?


    Thanks.


    Donna Bova

  • Do you use NXT?  How are you HIPAA Compliant?

  • Donna Roy:

    Does anyone have a standard practice for storing a donor's patient record number or date of encounter in the Raiser's Edge?

    We had originally uploaded the MRNs for our donor society members so we could quickly confirm their identity when coming across on our daily census report. We used the phone category of "Others"  with a phone type of MRN but were told by compliance that we had to take them out because we were at risk of HIPPA violation.  It worked really well while utilizing them this way.  It could be just our organizations interpretation of HIPPA, just something to keep in mind.  Also, we use the Alias field for employee numbers and this has worked really well to identify employees who may have had a name change, etc.

     
  • We renamed the Birthplace field to Employee ID.

    We use an alias for a "modified" medical record number - I think a beginning or ending digit has been removed so the ID is not exact but close enough to validate a matching name/address.

     
  • Donna Bova:

    Sue,


    Do you use NXT?  How are you HIPAA compliant?


    Thanks.


    Donna Bova

    We do not use NXT.  Yes, we are compliant.  We had to go through a lengthy process with the hospital compliance team and privacy officer to make sure the information we receive is allowable.  We are a state academic medical university in NY, so there were a lot of eyes on this before it was approved.

    Sue

     

  • HIPAA does allow Patient Biographic and certain elements of the visit to be shared with Institutional Advancement. We had the information that is shared with us reviewed by Compliance and legal to make sure we were within the boundries of what was allowed.


    We store the EPIC MRN and Campus Key (ID for all staff and students) as an Attribute. It makes for easy updates and access to the information. We screen our daily patient files. We use rolled up patient visit data to allow us to see a patients first visit with a Physcian, last visit and how many total visits to help us understand how long they have been coming and to also help identify the best Physican to work with as part of our Grateful Patient Program. The visit data is stored outside of RE in our ODS to allow for easier updating of the data and pulling into our reporting tools.

    Cheers,

    David
  • We store the patient ID as an Alias.. I don't know of any reports for which we use the number but it does distinguish our grateful patients from our regular donors. Unfortunately, NXT does not show Alais entries but I assume that is coming.


    Mark Guncheon

    Development IT Anaylst

    Bon Secours Health System

  • NXT does allow searching by Alias.
  • Hi there


    We have a separate database for our clients (we don't call them patients) and we store the unique ID from that database in the SSNum field which we've renamed to suit our purposes.


    If you do go with the Alias option, be aware that they can be quite sticky and difficult to remove. I suggest the trial and test idea proffered by Jen (I think) earlier is especially important so that you don't end up with a whole bunch of Aliases that are difficult to remove en masse. (Global delete doesn't remove the line, just the data in the line, then leaving blank lines of both alias type and alias name).

    I made the mistake of globally adding before testing and now I've got a whole stack of blank aliases when I made a global add!


    Good luck!

  • Andrew, I haven't used it, but Zeidman Development has a product called Alias Deleter, which should help you clean up any mess.  I don't know what the cost is, but it couldn't hurt to inquire.
  • Jen Claudy:

    NXT does allow searching by Alias.

    Yes, you can search but where do you see the alias in the person's record?

  • Currently, the Alias field is not visible in NXT...but you can search by it.  In the NXT Idea Bank, this Idea, to show the Aliases on a record, is marked as [Under Consideration] so be sure to go add your votes!
  • Jen Claudy:

    Currently, the Alias field is not visible in NXT...but you can search by it.  In the NXT Idea Bank, this Idea, to show the Aliases on a record, is marked as [Under Consideration] so be sure to go add your votes!

    Just voted. Thanks.

  • Jen Claudy:

    Currently, the Alias field is not visible in NXT...but you can search by it.  In the NXT Idea Bank, this Idea, to show the Aliases on a record, is marked as [Under Consideration] so be sure to go add your votes!

    Despite them being subject to change, there is a small note in the NXT Roadmap as follows:
    2018 Q1 - Field configuration (setting required and hidden fields); manage aliases; store credit card and bank info on constituent record directly

    This may mean that it is closer to implementation! (Hopefully)

  • @David Ritchie
    Hi David.

    We are a Medical Foundation attached to a hospital. We follow HIPPA with our grateful patient program. I am interested in finding out how you “segment” donors who are patients “within RE”? or even if that is considered HIPPA compliant.

    Thanks

    Potique

  • @Deb Dressely
    Can you explain this further please? What would a “modified” ID be and would you put it under the Alias or the Type?

  • @Potique Johnson We used the Alias field and our medical records team removed either a beginning character or the last character of the medical record number before sending us the data. The remaining characters were similar enough to allow us to validate it was the correct record but not complete so as to jeopardize confidentiality.

Categories