MDWS Scheduling in the VHA Innovations Sandbox

MDWS Scheduling in the VHA Innovations Sandbox

Disclaimer: I am a MDWS developer at VA and not directly involved in the VA Medical Appointment Scheduling Contest. My goal is to provide information on the web services that I develop, including guidance on strategies for using these services to generate rapid and reproducible results in ways that support long term success. You are not guaranteed any points or special consideration for your Scheduling Contest submission by incorporating any of the following recommendations.MDWS and the Scheduling APIs

What does MDWS have to do with the scheduling competition? We've exposed a number of easy to use web services that sit on top of the refactored scheduling APIs. The goal is for these services to enable all the functionality required for a scheduling solution across the VA enterprise. Web services were chosen as the medium due to their ease of use, cross platform nature and their being generally accepted as a modern development tool.  

 

Unfortunately, we are not yet ready to provide reproducible instructions that would enable one to create an end to end services based environment for the scheduling competition. It will be coming soon but there is still a bit of work to be done wrapping routines in RPCs, testing and patching bugs in the refactored APIs, building redistributable packages encapsulating it all, exposing the APIs in MDWS and testing them all, etc. However... all is not lost!

 

We've intentionally been performing this work for ourselves in an open environment so others may reap the benefits of our labor immediately (and also for transparency). That means there are currently internet accessible services for the scheduling competition. So, while you might not immediately be able to configure an environment of your own (at least not quickly or very easily), you can leverage the VHA Innovations Sandbox hosted services to get a jump on understanding this particular strategy. That is: web services, Vista refactoring, re-usable APIs and services, etc. 

 

The services are hosted at:

http://mdws.vistaehr.com/mdws2/SchedulingSvc.asmx

 

And, you can download the demo project's code which will show you how to use the web services:

git clone https://github.com/monkeyglasses/MDWS-Demo

 

Please join the weekly MDWS call to discuss! 

 

 

like0

Comments

MDWS Scheduling in the VHA Innovations Sandbox

Sam Habiel's picture

Joel,

I haven't seen any notes sent about the MDWS calls recently. Do you guys
send out a notice or is there a standing number and sharing site that you
use?

Thanks,

Sam

On Thu, Dec 20, 2012 at 4:27 AM, joelmewton <joel.mewton@va.gov> wrote:

> Disclaimer: I am a MDWS developer at VA and not directly involved in the
> VA Medical Appointment Scheduling Contest. My goal is to provide
> information on the web services that I develop, including guidance on
> strategies for using these services to generate rapid and reproducible
> results in ways that support long term success. You are not guaranteed any
> points or special consideration for your Scheduling Contest submission by
> incorporating any of the following recommendations. *MDWS and the
> Scheduling APIs*
>
> What does MDWS have to do with the scheduling competition? We've exposed a
> number of easy to use web services that sit on top of the refactored
> scheduling APIs. The goal is for these services to enable all the
> functionality required for a scheduling solution across the VA enterprise.
> Web services were chosen as the medium due to their ease of use, cross
> platform nature and their being generally accepted as a modern development
> tool. Also, MDWS provided a
>
>
>
> Unfortunately, we are not yet ready to provide reproducible instructions
> that would enable one to create an end to end services based environment
> for the scheduling competition. It will be coming soon but there is still a
> bit of work to be done wrapping routines in RPCs, testing and patching bugs
> in the refactored APIs, building redistributable packages encapsulating it
> all, exposing the APIs in MDWS and testing them all, etc. However... all is
> not lost!
>
>
>
> We've intentionally been performing this work for ourselves in an open
> environment so others may reap the benefits of our labor immediately (and
> also for transparency). That means there are currently internet accessible
> services for the scheduling competition. So, while you might not
> immediately be able to configure an environment of your own (at least not
> quickly or very easily), you can leverage the VHA Innovations Sandbox
> hosted services to get a jump on understanding this particular strategy.
> That is: web services, Vista refactoring, re-usable APIs and services, etc.
>
>
>
> The services are hosted at:
>
> http://mdws.vistaehr.com/mdws2/SchedulingSvc.asmx
>
>
>
> And, you can download the demo project's code which will show you how to
> use the seb wervices:
>
> git clone https://github.com/monkeyglasses/MDWS-Demo
>
>
>
> Please join the weekly MDWS call to discuss!
>
>
> --
> Full post:
> http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
> Manage my subscriptions:
> http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post:
> http://www.osehra.org/og_mailinglist/unsubscribe/1349
>

like0

MDWS Scheduling in the VHA Innovations Sandbox

Joel Mewton's picture

Hutch and I talked about Christmas shopping last week J

No one joined last Friday so no notes. The week before that... a few new
fellas joined and we chatted about Vista's security model and patient
identity across an enterprise like VA. I don't believe any notes were
taken though - sorry about that! The weekly call info can be found on
the MDWS group home page:

http://osehra.org/group/mdws

Here's the info:

Weekly calls on Fridays from 12:30 PM to 1:00pm EST.

https://osehra.webex.com/osehra/onstage/g.php?t=a&d=667800761
<https://osehra.webex.com/osehra/onstage/g.php?t=a&d=667800761>

Dial in: 1-650-479-3207 <tel:1-650-479-3207>

Access code: 667 800 761

No call this week, by the way. We will resume regularly scheduled calls
after the holidays on January 4th.

From: Sam Habiel [mailto:sam.habiel@gmail.com]
Sent: Thursday, December 20, 2012 11:42 AM
To: Mewton, Joel
Cc: MDWS
Subject: Re: [mdws] MDWS Scheduling in the VHA Innovations Sandbox

Joel,

I haven't seen any notes sent about the MDWS calls recently. Do you guys
send out a notice or is there a standing number and sharing site that
you use?

Thanks,

Sam

On Thu, Dec 20, 2012 at 4:27 AM, joelmewton <joel.mewton@va.gov> wrote:

Disclaimer: I am a MDWS developer at VA and not directly involved in the
VA Medical Appointment Scheduling Contest. My goal is to provide
information on the web services that I develop, including guidance on
strategies for using these services to generate rapid and reproducible
results in ways that support long term success. You are not guaranteed
any points or special consideration for your Scheduling Contest
submission by incorporating any of the following recommendations.

MDWS and the Scheduling APIs

What does MDWS have to do with the scheduling competition? We've exposed
a number of easy to use web services that sit on top of the refactored
scheduling APIs. The goal is for these services to enable all the
functionality required for a scheduling solution across the VA
enterprise. Web services were chosen as the medium due to their ease of
use, cross platform nature and their being generally accepted as a
modern development tool. Also, MDWS provided a

Unfortunately, we are not yet ready to provide reproducible instructions
that would enable one to create an end to end services based environment
for the scheduling competition. It will be coming soon but there is
still a bit of work to be done wrapping routines in RPCs, testing and
patching bugs in the refactored APIs, building redistributable packages
encapsulating it all, exposing the APIs in MDWS and testing them all,
etc. However... all is not lost!

We've intentionally been performing this work for ourselves in an open
environment so others may reap the benefits of our labor immediately
(and also for transparency). That means there are currently internet
accessible services for the scheduling competition. So, while you might
not immediately be able to configure an environment of your own (at
least not quickly or very easily), you can leverage the VHA Innovations
Sandbox hosted services to get a jump on understanding this particular
strategy. That is: web services, Vista refactoring, re-usable APIs and
services, etc.

The services are hosted at:

http://mdws.vistaehr.com/mdws2/SchedulingSvc.asmx

And, you can download the demo project's code which will show you how to
use the seb wervices:

git clone https://github.com/monkeyglasses/MDWS-Demo

Please join the weekly MDWS call to discuss!

--
Full post:
http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
Manage my subscriptions:
http://www.osehra.org/og_mailinglist/subscriptions
Stop emails for this post:
http://www.osehra.org/og_mailinglist/unsubscribe/1349

like0

ditto

Chris Uyehara's picture

ditto 

what Mr M(ewton) said ^-^

like0

SchedulingSvc

Ronald McLaren's picture

I downloaded the latest source for MDWS from GitHub, but it doesn't seem to contain the SchedulingSvc module.   

Would be possible to release this code as it would provide an invaluable resource to see what goes on "under the covers" even if it is not completely ready for production. I was also wondering when the final version of the code would be released...

I appologize if this information has been discussed during the conference calls (are there transcripts of what was discussed?). I have not had the opportunity to take part in them.

Thank You!

 

like0

MDWS Scheduling in the VHA Innovations Sandbox

Joel Mewton's picture

We did discuss this during the weekly MDWS calls but no worries. Some of the MDWS scheduling code has been committed to Github. We are in the process of posting the most recent bits. I will keep the group updated when that occurs. In the meantime, feel free to plug away at the services:

http://mdws.vistaehr.com/mdws2.8.0/SchedulingSvc.asmx

Thanks

From: Apache [mailto:apache@groups.osehra.org] On Behalf Of ronlaren
Sent: Sunday, February 03, 2013 7:40 PM
To: MDWS
Subject: Re: [mdws] MDWS Scheduling in the VHA Innovations Sandbox

I downloaded the latest source for MDWS from GitHub, but it doesn't seem to contain the SchedulingSvc module.

Would be possible to release this code as it would provide an invaluable resource to see what goes on "under the covers" even if it is not completely ready for production? I was also wondering when the final version of the code would be released...

I appologize if this information has been discussed during the conference calls. I have not had the opportunity to take part in them.

Thank You!

--
Full post: http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
Manage my subscriptions: http://www.osehra.org/og_mailinglist/subscriptions
Stop emails for this post: http://www.osehra.org/og_mailinglist/unsubscribe/1349

like0

VistA test instance

Ronald McLaren's picture

Is there a VistA test instance running somewhere with a test login I could use to excersize the MDWS demo?

Thanks again!

like0

MDWS Scheduling in the VHA Innovations Sandbox

Joel Mewton's picture

Are you referring to the demo here:

http://mdws.vainnovation.us/MdwsDemo

?? If so, just select the CPM database and use programmer1/1programmer for the A/V codes.

All the Vista servers in the Innovations sandbox are behind a firewall but MDWS is available on the internet as the proxy for communication.

From: Apache [mailto:apache@groups.osehra.org] On Behalf Of ronlaren
Sent: Saturday, February 16, 2013 10:05 AM
To: MDWS
Subject: Re: [mdws] MDWS Scheduling in the VHA Innovations Sandbox

Is there a VistA test instance running somewhere with a test login I could use to excersize the MDWS demo?

Thanks again!

--
Full post: http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
Manage my subscriptions: http://www.osehra.org/og_mailinglist/subscriptions
Stop emails for this post: http://www.osehra.org/og_mailinglist/unsubscribe/1349

like0

Thanks for the quick

Ronald McLaren's picture

Thanks for the quick reply!

Actually I was looking here: http://mdws.vistaehr.com/mdws2.8.0/SchedulingSvc.asmx

In order to call the "connect" and then the "login" api calls you need to have a VistA instance to connect to.

The "connect" api call takes the parameter sitelist, which I assume is a comma seperated list of URI's that point to VistA servers you want the MDWS instance to connect to. So I guess I'm asking if there is a VistA instance somewhere I could connect to (ie: I'm looking for a URI of an existing VistA instance I could connect to for testing/experimental purposes).

The "login" api call takes "username" and "pwd" parameters. I guess I would need a login and password for a test account I can use for these parameters for the particular VistA instance I've connected to..

 

like0

MDWS Scheduling in the VHA Innovations Sandbox

Joel Mewton's picture

Thanks for the clarification. See the unit test code here for the sequence of calls and the arguments (you should find some A/V codes in there) for using that web service endpoint:

https://github.com/monkeyglasses/MDWS-Demo/blob/master/trunk/MdwsDemo-Te...

You can exercise the web service through your browser – the code is just showing you what arguments to pass and the results you can expect.

From: Apache [mailto:apache@groups.osehra.org] On Behalf Of ronlaren
Sent: Saturday, February 16, 2013 11:18 AM
To: MDWS
Subject: Re: [mdws] MDWS Scheduling in the VHA Innovations Sandbox

Thanks for the quick reply!

Actually I was looking here: http://mdws.vistaehr.com/mdws2.8.0/SchedulingSvc.asmx

In order to call the "connect" and then the "login" api calls you need to have a VistA instance to connect to.

The "connect" api call takes the parameter sitelist, which I assume is a comma seperated list of URI's that point to VistA servers you want the MDWS instance to connect to. So I guess I'm asking if there is a VistA instance somewhere I could connect to (ie: I'm looking for a URI of an existing VistA instance I could connect to for testing/experimental purposes).

The "login" api call takes "username" and "pwd" parameters. I guess I would need a login and password for a test account I can use for these parameters for the particular VistA instance I've connected to..

--
Full post: http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
Manage my subscriptions: http://www.osehra.org/og_mailinglist/subscriptions
Stop emails for this post: http://www.osehra.org/og_mailinglist/unsubscribe/1349

like0

That worked. Thanks!

Ronald McLaren's picture

That worked. Thanks!

like0

getClinicSchedulingDetails Exception

Anthony Leonardi's picture

Hi I'm trying to run through the web services at http://mdws.vistaehr.com/mdws2.8.0/SchedulingSvc.asmx , but when I try to run getClinicSchedulingDetails (so that I can ultimately test makeAppointment), I get the following message returned:

*** Begin Exception String *** Exception Type: MdoException Error Code: 0 Error Code Value: Help Message: Message: Invalid response for building clinic scheduling details Source: mdo Stack Trace: at gov.va.medora.mdo.dao.vista.VistaSchedulingDao.toClinicSchedulingDetails(String[] response) in C:\workspace\MDWS\branches\vhaannmewtoj\mdo\mdo\src\mdo\dao\vista\VistaSchedulingDao.cs:line 105 at gov.va.medora.mdo.dao.vista.VistaSchedulingDao.getClinicSchedulingDetails(String clinicId) in C:\workspace\MDWS\branches\vhaannmewtoj\mdo\mdo\src\mdo\dao\vista\VistaSchedulingDao.cs:line 85 at gov.va.medora.mdws.SchedulingLib.getClinicSchedulingDetails(String clinicId) in C:\workspace\MDWS\branches\vhaannmewtoj\mdws\mdws\src\lib\SchedulingLib.cs:line 165 Target Site: gov.va.medora.mdo.HospitalLocation toClinicSchedulingDetails(System.String[]) *** End Exception String ***

it also returns a stack trace:

at gov.va.medora.mdo.dao.vista.VistaSchedulingDao.toClinicSchedulingDetails(String[] response) in C:\workspace\MDWS\branches\vhaannmewtoj\mdo\mdo\src\mdo\dao\vista\VistaSchedulingDao.cs:line 105 at gov.va.medora.mdo.dao.vista.VistaSchedulingDao.getClinicSchedulingDetails(String clinicId) in C:\workspace\MDWS\branches\vhaannmewtoj\mdo\mdo\src\mdo\dao\vista\VistaSchedulingDao.cs:line 85 at gov.va.medora.mdws.SchedulingLib.getClinicSchedulingDetails(String clinicId) in C:\workspace\MDWS\branches\vhaannmewtoj\mdws\mdws\src\lib\SchedulingLib.cs:line 165

I tried using clinic IDs: "12", "10", and "23" --> all returned the same message.

I attempted to look through the source on github, but it appears to be different from what's on the server.

Not sure if I'm looking for help with something I'm doing wrong, or just reporting a bug. Thanks for any help you can offer!

-Anthony

like0

MDWS Scheduling in the VHA Innovations Sandbox

Joel Mewton's picture

Hey Anthony,

I will take a look at this. IIRC, the clinics had to be set up correctly or the calls would bomb out. For example, if a clinic wasn’t configured with a valid start time value, the MDWS call would fail. This was by design since the correct configuration is essential to subsequent calls. I’m betting that’s the problem. In any event, I will look at these clinics on the server and see what’s up. Thanks for the good detailed info.

Oh, what site are you connecting to? Site 100, I presume?

From: Apache [mailto:apache@groups.osehra.org] On Behalf Of AJLeonardi
Sent: Monday, April 29, 2013 12:55 PM
To: MDWS
Subject: Re: [mdws] MDWS Scheduling in the VHA Innovations Sandbox

Hi I'm trying to run through the web services at http://mdws.vistaehr.com/mdws2.8.0/SchedulingSvc.asmx , but when I try to run getClinicSchedulingDetails (so that I can ultimately test makeAppointment), I get the following message returned:

*** Begin Exception String *** Exception Type: MdoException Error Code: 0 Error Code Value: Help Message: Message: Invalid response for building clinic scheduling details Source: mdo Stack Trace: at gov.va.medora.mdo.dao.vista.VistaSchedulingDao.toClinicSchedulingDetails(String[] response) in C:\workspace\MDWS\branches\vhaannmewtoj\mdo\mdo\src\mdo\dao\vista\VistaSchedulingDao.cs:line 105 at gov.va.medora.mdo.dao.vista.VistaSchedulingDao.getClinicSchedulingDetails(String clinicId) in C:\workspace\MDWS\branches\vhaannmewtoj\mdo\mdo\src\mdo\dao\vista\VistaSchedulingDao.cs:line 85 at gov.va.medora.mdws.SchedulingLib.getClinicSchedulingDetails(String clinicId) in C:\workspace\MDWS\branches\vhaannmewtoj\mdws\mdws\src\lib\SchedulingLib.cs:line 165 Target Site: gov.va.medora.mdo.HospitalLocation toClinicSchedulingDetails(System.String[]) *** End Exception String ***

it also returns a stack trace:

at gov.va.medora.mdo.dao.vista.VistaSchedulingDao.toClinicSchedulingDetails(String[] response) in C:\workspace\MDWS\branches\vhaannmewtoj\mdo\mdo\src\mdo\dao\vista\VistaSchedulingDao.cs:line 105 at gov.va.medora.mdo.dao.vista.VistaSchedulingDao.getClinicSchedulingDetails(String clinicId) in C:\workspace\MDWS\branches\vhaannmewtoj\mdo\mdo\src\mdo\dao\vista\VistaSchedulingDao.cs:line 85 at gov.va.medora.mdws.SchedulingLib.getClinicSchedulingDetails(String clinicId) in C:\workspace\MDWS\branches\vhaannmewtoj\mdws\mdws\src\lib\SchedulingLib.cs:line 165

I tried using clinic IDs: "12", "10", and "23" --> all returned the same message.

I attempted to look through the source on github, but it appears to be different from what's on the server.

Not sure if I'm looking for help with something I'm doing wrong, or just reporting a bug. Thanks for any help you can offer!

-Anthony

--
Full post: http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
Manage my subscriptions: http://www.osehra.org/og_mailinglist/subscriptions
Stop emails for this post: http://www.osehra.org/og_mailinglist/unsubscribe/1349

like0

Yup! site 100. thanks for the

Anthony Leonardi's picture

Yup! site 100.

thanks for the quick response.

like0

MDWS Scheduling in the VHA Innovations Sandbox

Joel Mewton's picture

Quick status update – I’m getting an error message that the entry we created in the OPTION file, “SD API”, for the scheduling RPCs is not installed on the server… I have no idea why as we’ve used these APIs in demos on a few different occasions. I see version T4 of the scheduling KIDS is installed. I’m trying to install T7 to see if that fixes it but I’m having a rough go with it receiving errors that GT.M can’t access the file system to load the KIDS… I’m going to keep plugging away at it. Just thought I’d give you some more info.

More soon…

From: Apache [mailto:apache@groups.osehra.org] On Behalf Of AJLeonardi
Sent: Monday, April 29, 2013 1:12 PM
To: MDWS
Subject: Re: [mdws] MDWS Scheduling in the VHA Innovations Sandbox

Yup! site 100.

thanks for the quick response.

--
Full post: http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
Manage my subscriptions: http://www.osehra.org/og_mailinglist/subscriptions
Stop emails for this post: http://www.osehra.org/og_mailinglist/unsubscribe/1349

like0

MDWS Scheduling in the VHA Innovations Sandbox

Sam Habiel's picture

Joel,

You need to convert the line endings on the KIDS file to be Unix Line endings.

Sam

On Mon, Apr 29, 2013 at 1:03 PM, "Mewton, Joel" <Joel.Mewton@va.gov> wrote:
> Quick status update – I’m getting an error message that the entry we created
> in the OPTION file, “SD API”, for the scheduling RPCs is not installed on
> the server… I have no idea why as we’ve used these APIs in demos on a few
> different occasions. I see version T4 of the scheduling KIDS is installed.
> I’m trying to install T7 to see if that fixes it but I’m having a rough go
> with it receiving errors that GT.M can’t access the file system to load the
> KIDS… I’m going to keep plugging away at it. Just thought I’d give you some
> more info.
>
>
>
> More soon…
>
>
>
> From: Apache [mailto:apache@groups.osehra.org] On Behalf Of AJLeonardi
> Sent: Monday, April 29, 2013 1:12 PM
> To: MDWS
> Subject: Re: [mdws] MDWS Scheduling in the VHA Innovations Sandbox
>
>
>
> Yup! site 100.
>
> thanks for the quick response.
>
> --
> Full post:
> http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
> Manage my subscriptions: http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post:
> http://www.osehra.org/og_mailinglist/unsubscribe/1349
>
>
> --
> Full post:
> http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
> Manage my subscriptions: http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post:
> http://www.osehra.org/og_mailinglist/unsubscribe/1349
>

like0

MDWS Scheduling in the VHA Innovations Sandbox

Joel Mewton's picture

Thanks for the tip, Sam! I ran the dos2unix command on the file and
verified with vi but still no dice. Any idea how I specify the path to
the file from inside GT.M? Maybe that's what I'm doing incorrectly? I
tried putting in the root of the filesystem as well as inside the GT.M
install path but both give the same error: "Couldn't open file or HFS
device"

-----Original Message-----
From: Apache [mailto:apache@groups.osehra.org] On Behalf Of Sam Habiel
Sent: Monday, April 29, 2013 4:13 PM
To: mdws@groups.osehra.org
Subject: Re: [mdws] MDWS Scheduling in the VHA Innovations Sandbox

Joel,

You need to convert the line endings on the KIDS file to be Unix Line
endings.

Sam

On Mon, Apr 29, 2013 at 1:03 PM, "Mewton, Joel" <Joel.Mewton@va.gov>
wrote:
> Quick status update - I'm getting an error message that the entry we
> created in the OPTION file, "SD API", for the scheduling RPCs is not
> installed on the server... I have no idea why as we've used these APIs

> in demos on a few different occasions. I see version T4 of the
scheduling KIDS is installed.
> I'm trying to install T7 to see if that fixes it but I'm having a
> rough go with it receiving errors that GT.M can't access the file
> system to load the KIDS... I'm going to keep plugging away at it. Just

> thought I'd give you some more info.
>
>
>
> More soon...
>
>
>
> From: Apache [mailto:apache@groups.osehra.org] On Behalf Of AJLeonardi
> Sent: Monday, April 29, 2013 1:12 PM
> To: MDWS
> Subject: Re: [mdws] MDWS Scheduling in the VHA Innovations Sandbox
>
>
>
> Yup! site 100.
>
> thanks for the quick response.
>
> --
> Full post:
> http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
> Manage my subscriptions:
> http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post:
> http://www.osehra.org/og_mailinglist/unsubscribe/1349
>
>
> --
> Full post:
> http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
> Manage my subscriptions:
> http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post:
> http://www.osehra.org/og_mailinglist/unsubscribe/1349
>

like0

RE: MDWS Scheduling in the VHA Innovations Sandbox

Catalin Branea's picture

Remember that paths in Linux are case sensitive, so in my system I enter something like:

/home/softhat/kids/SD_RPC.KID

Catalin

like0

MDWS Scheduling in the VHA Innovations Sandbox

Joel Mewton's picture

Thanks for the tip, Catalin. Turns out I was specifying the wrong path altogether. Sam “The Man” Habiel showed me a few tricks and I’ve got the latest patch installed. Thanks again, Sam!

Anthony – I just verified the call to getClinicSchedulingDetails works now. I ran through pretty much every other call to make sure I didn’t receive any other errors and they all swell, too.

Bam.

From: Apache [mailto:apache@groups.osehra.org] On Behalf Of catalinb
Sent: Monday, April 29, 2013 11:16 PM
To: MDWS
Subject: Re: [mdws] MDWS Scheduling in the VHA Innovations Sandbox

Remember that paths in Linux are case sensitive, so in my system I enter something like:

/home/softhat/kids/SD_RPC.KID

Catalin

--
Full post: http://www.osehra.org/wiki/mdws-scheduling-vha-innovations-sandbox
Manage my subscriptions: http://www.osehra.org/og_mailinglist/subscriptions
Stop emails for this post: http://www.osehra.org/og_mailinglist/unsubscribe/1349

like0