Jump to content
Sign in to follow this  

Logic Check

Recommended Posts

I'm just starting to play with the demo to see if it will work for my solution - I'm pretty darn sure it will just don't know how to do it.

Here's the situation: Want to store scanned copies of forms to a db. The problem is that each patient will have multiple forms and in some cases multiple copies of each form.

Directory Structure so far:



Here's the logic I'm working under so far:

Can't use WebViewer as each patient will have multiple images so I need to resort to the portal method. First off, if this is an incorrect assumption, please tell me what I'm missing.

Since SC only prefers 1 file per folder and my relationship for the portal is the PatientID, need to manually create the sub-directory for the new form.

To add a form, use the SCChooseFile to allow the user to find the local file. If valid, lookup the PatientID in the Patients_SC db and get the found count. Add 1 to that number and embed that into the path so a new form for patient 1008 would be:


if this were the 8th form added.

Using the demo copy, I'm building the cResourceIdentifier field (since it's already setup to use that one) and changed it from a calculation to a static text (could probably figure out how to leave it a calc later) and build it on the fly based on script parameters passed in (namely "Patients", "Forms", and "[PatientID]". Reason is that if this works, I will also setup a db for Doctors forms and letters.

So, what's wrong with my logic? Anything? As will all programming problems, there are numerous ways to solve them. I'm just trying to find the simplest for now.


Share this post

Link to post
Share on other sites

I think you're doing the same thing, I'm about to advise... but here it goes

I would setup a separate FileMaker table - Forms

this table would contain your

baseURL calc - "http://serverAddress:portNumber/SuperContainer/Files"

folderPath calc - Forms::RecordID

it would have a foreign key to Patients, that would be used to related documents to a patient

You could have another simmilar table for letters, but I think that you could just store both in Forms table, maybe rename it Documents, by adding a type field to distinguish between forms and letters.

Feel free to give me a call to discuss if you feel that by phone it would be easier.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  


Important Information

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