Tracker: Bugs

5 Update local not updating data on CCAP - ID: 2843610
Last Update: Comment added ( lbell33 )

Mozilla
August 24th/09
11:01am
Build: August 18th/09

Hi Marc,

Not sure on the delay between QA3 and CCAP.

I updated client MARY JANE, in Off the Streets Program on caisi QA3
facility on QA3.
I changed her birth date and health card number
I then logged into qaccap.caisi.ca
Updated local, since she was already registered in Test Program
Her HIN and birth date were unchanged.

However, in relation to the previous bug I logged, her issues now only
included the one I had written as oscar doc, post-schizophrenic
depression.

Lauren


Lauren Bell ( lbell33 ) - 2009-08-24 15:12

5

Open

None

Marc Dumontier

CAISI Case Managemnt Encounter

OSCAR Main Trunk

Public


Comments ( 3 )




Date: 2009-09-04 04:42
Sender: lbell33

Sure that makes sense. But for the purposes of the CCAP, "update local"
becomes very confusing. I believe the way the CCAP was setup was that even
once the client is "discharged" after a 72 hour period, they will still
always come up as a local match. Is this not really problematic in that the
system will still be referencing their original "copy to local"
data.....ie. if a client comes back 2 years later, the data will be
extremely inaccurate...and there is no way for someone using the ER Clerk
role to update the data themselves.


Date: 2009-09-03 17:10
Sender: tomislavsvoboda

not a bug, the integration should work this way....ie each agency has it's
own version of the tombstone data which it can change as it sees fit

t



Date: 2009-09-02 23:04
Sender: hexbinary

upload local has nothing to do with the integrator. it will only show you
the local instance data. Copy to local is the only time that data is moved
from the integrator to the instance.

I guess there's no current way to "update" the client file. That probably
needs to be discussed.


Log in to comment.

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.