Client 214 betas

The link to the latest Beta is here, but you need to sign up for a login here first.

Take me thru all the steps to get this error, and what server are you using?

[F7] - ticklers, fill it out, click [save tickler] .. error.

tickler doesn't save.

Noted.

[quote user="Jason"]

[F7] - ticklers, fill it out, click [save tickler] .. error.

tickler doesn't save.

[/quote]

For those looking for a very temporary workaround for the Tickler Saving issue.

Beta24 worked for me.

All betas from 1 to latest give my secretary this popup when she hits last scan.

The popup can be closed down and as it turns out... the last scan does appear ... but my secretary is going crazy with

This latest round of betas has created more bugs than we've seen for at least a year and I would like to have a stable client for my secretary to use: ie. 213.

I've tried 10 betas all have the same problems.

She says other popups are happening randomly as well.

What you're seeing is that Synapse is looking at the file name to see if it matches the autofile naming convention.

If it does, it then searches to see if that filename matches any patient in the system.

It's not finding any patients and so gives those messages.

maybe I can turn them off.

Pls give me an example of the file naming convention you are using for the scanned files.

2008_07_15_18_21_13.pdf


The messages shouldn't popup.

<h2 class="editable">R214B33 for Windows (client)</h2>

• Fixes a new bug with saving ticklers
• The
  status field is now updated if a match can not be found for a patient
  based upon parsing the filename rather than showing a popup
• You can create and save clinical pathways, but saving content of nodes is not debugged yet

<h2 class="editable">R84B8 for Windows (server)</h2>

• Supports creating, and saving clinical pathways

<h2 class="editable">
</h2>

The Beta-33 client is being released early to fix the tickler bug. The clinical pathways editor is not fully debugged yet.

Here's how to load a sample pathway

In the encounter editor

1. Click on the [Add New Pathway] button bottom right
2. Enter dummy in the requester
3. On the blank canvas, type control-i
4. Enter http://synapse-clinical-pathways.s3.amazonaws.com/rheumatoid-arthritis
5. This then saves the rheumatoid-arthritis map to the new maps directory
6. Now, type control-L, and navigate to the maps directory, select the rheumatoid-arthritis map
7. Now to save it, type control-S to save it - enter "created" or something in the requester
8. Close the encounter editor down.
9. Restart the encounter editor, and the rheumatoid-arthritis map now appears in the Clinical Pathways table

To create a new pathway denovo

1. Click on the [Add New Pathway] button bottom right
2. Enter the name of the pathway in the requester
3. Double click on the canvas to create a node
4. Double click on the node to edit it ( the title is currently only saved )
5. Repeat to create more nodes.
6. Drag from the bottom left corner to another node to link them
7. Control-S to save it

** Access Error: Cannot open /C/EMR/Client/synapse/3flex.preferences
** Near: prefs: construct load %synapse/3flex.preferences
default-font-small:
** Press enter to quit...




I take it I need the latest server to run the latest beta ?

ok, it was late at night !

Try beta-34

Works.

B34 works as well.

B34's "no name match" [Last File] popups are now gone being replaced by the much more convenient Status messages !

For those of you getting an expired client message, you can download the beta-35 from

http://demo-client.s3.amazonaws.com/synapse.exe

This client works with the demo server and also a localhost server setup on the same PC you are using.

Could we shorten the new beta to maybe 6 weeks to minimize old client problems ?

I think the more casual synapse users that dont participate on the forums would appreciate it []

What do you mean?

• Client 214 betas 31 March 2008
• Client 213 Final released 30 Mar 2008
• Client 213 betas 24 Dec 2007
• Client 212 betas 25 Oct 2007
• Client 211 Final released 24 Oct 2007
• Client 211 betas 29 Sep 2007
• Client 210 recently
• Client 209 19 June 2007
• Client 208 23 April 2007
• Client 206 1 April 2007
• Client 205 25 March 2007
• Client 203 7 March 2007

The clients and their 3 month expiry dates will cause problems if a new client isn't released every 3 months.

2 options

(1) release new clients q 2 months, clients expire every 3 months

(2) release clients every 2-4 months, clients expire every 6 months.

?

If more people used the betas and reported any errors found, it would speed up the developement cycle.