|
Post by jubilee on Dec 30, 2018 17:57:19 GMT -6
I have been using a demo version of Crystal to create a new template. We are fairly happy with it, and ready to go live with it for the new year.
I have backed up the template in the demo version, but wondering how to get it on our live version. We are in a terminal service environment. I tried to upload it so we could just search and pull it off from our system, but received an error message due to the demo status it was being uploaded from.
Thanks!
|
|
|
Post by erica on Dec 31, 2018 9:15:00 GMT -6
Hello, if you are running the demo on your local computer, you can back up the file Go to EHR->Import Templates/MedRec Utility Click the Backup Existing Templates button, save the file to your desktop (it's best to leave the name the default name)
Right click the file and copy it In your remote desktop, right click on the desktop and paste the file.
In your live version of crystal: Go to Admin->Company->Records and make sure there is a check next to Versioning of Medical Record Templates Go to EHR->Import Templates/MedRec Utility Click the Backup Existing Templates button and save the file to your documents. Now you will have a set of gray buttons. Click Restore Med Recs from Backup and choose the file you transfered. You will see a prompt when the template is loaded, it usually just takes a few seconds.
You will see this change on new records that are created.
If you have any issues, let me know.
|
|
|
Post by jubilee on Jan 1, 2019 12:28:31 GMT -6
Got the template switched. The issue I didn't think through is with such a radical change, how to pull the information from the old template into the new template.
If the family history was in field 1354 in the old template, but 2158 in the new, would the scripting to pull that forward still work?
|
|
|
Post by erica on Jan 1, 2019 14:02:41 GMT -6
There isn't an easy way to do this - generally you'll access the old info in Old Records at the bottom. You can create a button to bridge the gap between the old template and the new template. You would need a list of the old ID and the new ID. This is how the button setup would look like: You could make one button that pulls in all of the previous fields you want or separate buttons for each section. The pro is the obvious that you can pull through the previous exam info. The con is that depending on how many fields you need it could take a while to gather the info/program the button. Also you would only use the button one time to bridge the gap. Let em know if you have any questions. Erica
|
|
|
Post by jubilee on Jan 1, 2019 14:09:54 GMT -6
That's what I am trying currently trying, making a button to pull forward Ocular/medical histories, last RX, and certain notes. My only other complication in this matter is our old template had checkboxes for the patient/family history. Our new one does not. Trying to figure out how to convert a checkbox under Mother in the old template, to fill in Mother (or parent) in the new field.
|
|
|
Post by focusopsd on Jan 6, 2019 12:52:22 GMT -6
Erica,
Where can I find the list of all the available commands (STV, SPF, ...) or resources talking about it?
Thanks!
|
|
|
Post by paremyd on Jan 14, 2019 8:06:39 GMT -6
Erica, Where can I find the list of all the available commands (STV, SPF, ...) or resources talking about it? Thanks! I don't know where I got this, but I had to scan this and attach. I hope that it is useful. key to button commands and fid codes.pdf (372.43 KB)
|
|
|
Post by focusopsd on Jan 17, 2019 8:39:50 GMT -6
Erica, Where can I find the list of all the available commands (STV, SPF, ...) or resources talking about it? Thanks! I don't know where I got this, but I had to scan this and attach. I hope that it is useful. Thanks for that ... I did get the same document from CPM Team ^_<
|
|
|
Post by erica on Jan 17, 2019 9:45:43 GMT -6
|
|
|
Post by mdeyedoc on Jan 21, 2019 11:51:44 GMT -6
You can create a button to bridge the gap between the old template and the new template. You would need a list of the old ID and the new ID. This is how the button setup would look like: You could make one button that pulls in all of the previous fields you want or separate buttons for each section. The pro is the obvious that you can pull through the previous exam info. The con is that depending on how many fields you need it could take a while to gather the info/program the button. Also you would only use the button one time to bridge the gap. Let em know if you have any questions. Erica
I haven't had much spare time so I haven't been in the forums lately but I just noticed this comment. Am I understanding correctly that the *spf command will create a crosswalk for moving your stored FID values from from one template to the equivalent FIDs in the new template so the Prev values and auto history would display the correct values when using the new template?
If so:
You create this button and run it one time to transfer all the data? Does it only effect the records produced under the new template? IE, with versioning turned on, can you still view the prior records using previous template and the field data will be correct?
- Can you do this after data has already been entered in the new template? IE if you switched 6 mos ago, can you still transfer?
Obviously, there may be some fields where there is no 1:1 correlation and you'd just lose the prev/auto history on those. It would be a lot of work but also a huge advantage to have that previous data available to under the new template.
Marcia
|
|
|
Post by paremyd on Jan 28, 2019 10:15:47 GMT -6
Can someone answer Marcia's questions?
This might be helpful to us too.
Thanks!
|
|
|
Post by erica on Jan 28, 2019 11:22:46 GMT -6
You can create a button to bridge the gap between the old template and the new template. You would need a list of the old ID and the new ID. This is how the button setup would look like: You could make one button that pulls in all of the previous fields you want or separate buttons for each section. The pro is the obvious that you can pull through the previous exam info. The con is that depending on how many fields you need it could take a while to gather the info/program the button. Also you would only use the button one time to bridge the gap. Let em know if you have any questions. Erica
You create this button and run it one time to transfer all the data? Yes, this button can include any field you want to transfer info from. It will grab the info from the last time the field was filled out. So as long as the old fields are on the same date of service it should work well. The only problem I can see as you listed below where there is no 1:1 correlation is if the old field ID was DOS 01/01/2016 and one of the shared fields was filled out on 01/01/2018, it would only pull the information from the most recent record. I hope that makes sense. I would keep this button separate from other previous buttons. Does it only effect the records produced under the new template? IE, with versioning turned on, can you still view the prior records using previous template and the field data will be correct? Correct, it's just a button that you would add to the template and use as needed. - Can you do this after data has already been entered in the new template? IE if you switched 6 mos ago, can you still transfer?
- Yes, it sort-of ties into the first question.
I hope this helps?
|
|
|
Post by jubilee on Feb 4, 2019 19:20:46 GMT -6
I ended up creating a "Port from old template" button for the first time we see a patient under the new one. Most of it ports over okay, though changing from check boxes to drop downs is a bit problematic. I eventually created checkboxes to reside temporarily next to our one line boxes to allow us to see the info on the current template, and then choose the correct drop down option w/o having to tab back and forth, or ask the question again.
|
|
|
Post by mdeyedoc on Feb 11, 2019 21:52:51 GMT -6
You create this button and run it one time to transfer all the data? Yes, this button can include any field you want to transfer info from. It will grab the info from the last time the field was filled out. So as long as the old fields are on the same date of service it should work well. The only problem I can see as you listed below where there is no 1:1 correlation is if the old field ID was DOS 01/01/2016 and one of the shared fields was filled out on 01/01/2018, it would only pull the information from the most recent record. I hope that makes sense. I would keep this button separate from other previous buttons. Does it only effect the records produced under the new template? IE, with versioning turned on, can you still view the prior records using previous template and the field data will be correct? Correct, it's just a button that you would add to the template and use as needed. - Can you do this after data has already been entered in the new template? IE if you switched 6 mos ago, can you still transfer?
- Yes, it sort-of ties into the first question.
I hope this helps? Ah… I misunderstood what this button function does. I thought it allowed you to transfer the FID data from one FID to another so that you could see the historical values in the fields history drop down (F12).
Just to make sure I understand, the *SPF button command just fills the most recent data value for the original FID into the corresponding matched FID on the new medical record, regardless of the date the original FID data came from. E.G. If the most recent data for the FID for IOP contains data is from 8/1/18 and the most recent data for OD the FID for cornea is from 11/1/18, both will fill the corresponding FIDs in the current medical record, correct?
That helps a little but it would be REALLY nice if you could copy the entire history to the new FIDS. In order to do that the database would have to be modified to track separate FID values for each template so the previous templates would still work with versioning. That would use more data but text data doesn’t take up much memory. You also wouldn’t want to create a new version every time any little change is made.
IMO, a version should only be designated as a new version if you’re switching to an entirely different template where the FIDs don’t match. Just making changes in layout or adding buttons, extra fields, etc on the same template should not constitute a new version. If someone decides to use a new template, they should be able to mark it as new when the system is restored to the new database and the system and the system could then flag that the last template as the one to be used for previous records.
Marcia
|
|
|
Post by erica on Feb 12, 2019 8:23:07 GMT -6
Ah… I misunderstood what this button function does. I thought it allowed you to transfer the FID data from one FID to another so that you could see the historical values in the fields history drop down (F12).
Just to make sure I understand, the *SPF button command just fills the most recent data value for the original FID into the corresponding matched FID on the new medical record, regardless of the date the original FID data came from. E.G. If the most recent data for the FID for IOP contains data is from 8/1/18 and the most recent data for OD the FID for cornea is from 11/1/18, both will fill the corresponding FIDs in the current medical record, correct? No, the data wouldn't be filled from different dates, it all comes from the same date.
IMO, a version should only be designated as a new version if you’re switching to an entirely different template where the FIDs don’t match. That's how it was implemented.
|
|