Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About TWillson

  • Rank

Profile Information

  • Gender
  • Location
    New Jersey
  1. I am providing home Physical Therapy services to infants and required to write a note which parent and I both sign (I would like to do this digitally using FM Go, and sync with a FM Advance on a laptop computer.) The state I am working in has the following requirements for electronic records: * Record itself must meet the general and specific requirements of the regulations as to content. * Possible to determine when the record was created. * Process to prevent records from being altered after they are created. * If records can be altered, alteration process is documented. * Actual caregiver identified in the record. * Caregiver identified as having selected menu entries. * System of internal controls that insures that actual completed service delivery drives Medicaid billing. * Records should be maintained in the ordinary course of business so that no "special" programming, software, language, etc., is required to access them. I am using timestamps, audit logs and tracking database access by account login. My question is regarding electronic signatures, specifically the parent signature. Below are two ideas I have for attaching the signature to the note and to prevent editing of the signed document: 1)generate a pdf (locked by a random password) with the parents signature (which is cleared after the pdf is generated), and store the pdf in a container field for printing (I need to submit printed copies.) The issue I anticipate is regarding database size. Each pdf would be 196 KB, with approx 10 new records per week. 2)capture and store the parent’s signature in a table along with a hash of the note at the time of signing. When printing, generate a hash of the note, so that the parent’s signature will only appear if the session note hasn’t been modified. The issue I have relates to me being both the developer and user. Couldn’t I technically have the ability to make changes to the note and re-hash to have the signature appear? Is it possible to lock down the signature table (even from the developer (me)) when removing Full Access to prevent ever changing the hash or duplicating the signature? Any thoughts or feedback on either of the two scenarios would be much appreciated. Thanks, Tom
  2. I am also using this method to create related records (just updating some old "create related record" scripts in a multi-user database). Just a quick question about the initial test in your script. Are there any issues with using a loop to check if a valid relationship exists before proceeding with the creation of a new record rather than exiting the script and forcing the user to re-submit? Tom
  3. Mike, You can use a portal to hide the button (as well as other objects on the layout). When the relationship a portal is based on is invalid, the portal will disapear along with any objects contained within it. Build a self relationship which is valid only when the administrator, or someone from the administrator group is logged into the database. Place the button inside the portal. When a user logs in who does not have administrator privleges the portal will disappear along with the button. There should be some examples from the professionals on this board floating around. If not let me know and I will put one up. Tom
  4. Jim Thank you for the example, it seems to be along the same lines as what Vaughan had suggested and is exactly what I am looking for (although I may automate the closing of a status event when a user tries to create a new one). I'm spending some time now reading through the scripts. Thanks again for the advice, it is greatly appreciated. Tom
  5. Thanks for the feedback Vaughan. I think your suggestion of having each related record represent the number of days of the athlete being on a particular status would make things a lot more flexible as far as reporting (rather than keeping a running total of the number of days an athlete is on each status). So than my script to record the end date would look something like: Go to Related Record [AthleteDemographics::ID=AthleteStatus::AtheteID] # Sorted by Start Date, descending Set Field [AthelteDemographics::ID=AthleteStatus::AthleteID], Status(CurrentDate) The script would than continue to create a new status record, setting the start date to the current date and leaving the end date open. Sound right? Thanks Tom
  6. I am currently working on a database for the documentation of athlete's injuries and their playing status. I would like to run a report which shows the number of days an athlete has been able, limited or unable. I have a main database with athlete demographic information and a separate related database for athlete status (i.e. able, limited, unable). A new record is created in the athlete status database each time their status changes. An athlete's status may change daily, weekly or monthly. I was planning on setting up three text fields in the athlete status database. One each to keep a running total of the number of days an athlete was able, limited or unable. Each time a new record was created in the athlete's status database the number of days they were able, limited or unable would be calculated and appended to the running total fields. Does anybody have any suggestions on a better way to set this up. It would be nice to calculate the number of days an athlete was at a particular status "on the fly" with a looping script, however this seems like it would be too complicated. Thanks, Tom
  7. Charlie, I'm not sure if this is 100%, but others have reported it, I believe on this forum, with a few different mouse configurations. If you hide the status area, it seems the mouse scroll wheel no longer scrolls records. Actually, to make sure users need to use custom scripts in order to scroll records I have utilized a seperate database just for the front end which only has one record to display the data. I understand there are many limitations to this setup but it seems to be working for my setup so far. Tom
  8. Lilian, I am not a database programmer by trade and had limited experience with Microsoft Access before switching to Filemaker a short time ago. Many of the somewhat easy tasks I was struggeling with in Access and trying to learn VBA (with no programming experience) have been accomplished much easier with Filemaker with a much shorter learning curve. I definitely agree with Peter, these forums are a huge help. You may want to spend some time just reading through posts to get an idea of the possiblities, tips and tricks. What has also helped me is to download sample databases and just spending time figuring out how they work i.e use of scripts, calculations, portals etc. I also suggest another book which has been a big help to me and I know other have recommended this as well: "Advanced FileMaker Pro 5.5 Techniques for Developers" by Chris Moyer and Bob Bowers. Hope this helps, Tom
  9. Is it good design to seperate the user interface from the data in filemaker. This was the case in Access and allowed you to make changes to the UI without have to do imports/exports. At first I did not think this was possible, but as I learn more about scripts, portals, constants and globals I see this is very possible. Are there any implications with seperating the two in a multiuser environment? Thanks, Tom
  10. Thanks for the advice, just wanted to make sure. I actually took a few days off from working on this database (only part-time), and have been reading through a lot of the posts here. These forums have been a huge help to me. Thanks, Tom Willson
  11. I have a question regarding the way I am using portals in my database. I am new to Filemaker and have just begun to learn about scripts and calculations. My database is used for patient records. I would like to keep track of various other service providers that these patients see, such as orthotists, medical clinics, doctors etc. I have a contacts database which lists all the other service providers and need to associate them with the patient record. Originally I just used a lookup field to pick the contacts unique ID number, used relationship fields to show some of their basic info and a button which would go to the related record. However this seemed complicated and limited the number of contacts displayed in the patient record. Alternatively, (based on an example from the book "Advanced FileMaker Pro 5.5 Techniques for Developer") I have set up a portal in the main patient database which lists all the contacts from the contacts database (relationship based on a calculated field in both databases with a value equal to one). When I select a contact a new record is created in a third database "paientscontacts", which copies the patients unique ID and the contacts uniqe ID into a new record. I than have a second portal setup to show all the related contacts for that patient. Am I on the right track with this, or is there a better way to set this up? Thank you, Thomas Willson
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.