problem while connecting Master Patient Index

While using FOIA-VistA got following error. Do we have to different setup for MPI connection? Select PATIENT NAME: ZZTEST, ONE ARE YOU ADDING 'ZZTEST,ONE' AS A NEW PATIENT (THE 2ND)? No// Y (Yes) PATIENT SEX: F FEMALE PATIENT DATE OF BIRTH: 341960 ?? DOB Enter the patient's DATE OF BIRTH which must be later than 12/31/1870. DAT E OF BIRTH cannot be a date after the beneficiary 'Ineligible Date' or a date af ter the 'Enrollment Application Date'. Examples of Valid Dates: JAN 20 1957 or 20 JAN 57 or 1/20/57 or 012057 T (for TODAY), T+1 (for TOMORROW), T+2, T+7, etc. T-1 (for YESTERDAY), T-3W (for 3 WEEKS AGO), etc. If the year is omitted, the computer uses CURRENT YEAR. Two digit year assumes no more than 20 years in the future, or 80 years in the past. You may omit the precise day, as: JAN, 1957 PATIENT DATE OF BIRTH: 03041960 (MAR 04, 1960) PATIENT SOCIAL SECURITY NUMBER: 56544445656 ?? SSN Enter 9-digit SSN or 'P' for pseudo-SSN. PATIENT SOCIAL SECURITY NUMBER: 565445678 PATIENT TYPE: ? Choose from the available listing the PATIENT TYPE which best classifies th is patient. Enter the patient type for this patient. This is selectable from the distributed entries in the TYPE OF PATIENT file. The type selected should be the primary one selectable. For example, if the patient is both an ... Answer with TYPE OF PATIENT NAME Choose from: ACTIVE DUTY ALLIED VETERAN COLLATERAL EMPLOYEE MILITARY RETIREE NON-VETERAN (OTHER) NSC VETERAN SC VETERAN TRICARE PATIENT TYPE: NON-VETERAN (OTHER) PATIENT VETERAN (Y/N)?: N NO PATIENT SERVICE CONNECTED?: N NO PATIENT MULTIPLE BIRTH INDICATOR: N NO ...searching for potential duplicates No potential duplicates have been identified. ...adding new patient...new patient added Patient name components-- FAMILY (LAST) NAME: ZZTEST// GIVEN (FIRST) NAME: ONE// MIDDLE NAME: PREFIX: SUFFIX: DEGREE: Press ENTER to continue Please verify or update the following information: MOTHER'S MAIDEN NAME: DUCK PLACE OF BIRTH [CITY]: SAN ANTONIO PLACE OF BIRTH [STATE]: TEXAS Select ALIAS: *Attempting to connect to the Master Patient Index in Austin...* *If no SSN or inexact DOB or common name, this request* *may take some time, please be patient...* * * * * *Could not connect to MPI or Timed Out, assigning local ICN (if not already assig* *ned)...* *%GTM-E-UNDEF, Undefined local variable: Y(0)*
like0

Comments

problem while connecting Master Patient Index

conor dowling's picture

Jignesh

Both world and openvista comment out or change a bunch of registration logic - one item is this MPI call. If you look at the registration package analysis in vista analytics, it lists the changes. We are going to talk about them into tomorrows tools call

Sent from my iPhone

On Mar 6, 2012, at 12:10 PM, Jignesh Patel <jigneshmpatel@gmail.com> wrote:

> While using FOIA-VistA got following error. Do we have to different setup for MPI connection?
>
>
>> Select PATIENT NAME: ZZTEST, ONE
>> ARE YOU ADDING 'ZZTEST,ONE' AS A NEW PATIENT (THE 2ND)? No// Y (Yes)
>> PATIENT SEX: F FEMALE
>> PATIENT DATE OF BIRTH: 341960 ??
>> DOB
>> Enter the patient's DATE OF BIRTH which must be later than 12/31/1870. DAT
>> E OF BIRTH cannot be a date after the beneficiary 'Ineligible Date' or a date af
>> ter the 'Enrollment Application Date'.
>> Examples of Valid Dates:
>> JAN 20 1957 or 20 JAN 57 or 1/20/57 or 012057
>> T (for TODAY), T+1 (for TOMORROW), T+2, T+7, etc.
>> T-1 (for YESTERDAY), T-3W (for 3 WEEKS AGO), etc.
>> If the year is omitted, the computer uses CURRENT YEAR. Two digit year
>> assumes no more than 20 years in the future, or 80 years in the past.
>> You may omit the precise day, as: JAN, 1957
>> PATIENT DATE OF BIRTH: 03041960 (MAR 04, 1960)
>> PATIENT SOCIAL SECURITY NUMBER: 56544445656 ??
>> SSN
>> Enter 9-digit SSN or 'P' for pseudo-SSN.
>> PATIENT SOCIAL SECURITY NUMBER: 565445678
>> PATIENT TYPE: ?
>> Choose from the available listing the PATIENT TYPE which best classifies th
>> is patient.
>> Enter the patient type for this patient. This is selectable from the
>> distributed entries in the TYPE OF PATIENT file. The type selected should
>> be the primary one selectable. For example, if the patient is both an
>> ...
>> Answer with TYPE OF PATIENT NAME
>> Choose from:
>> ACTIVE DUTY
>> ALLIED VETERAN
>> COLLATERAL
>> EMPLOYEE
>> MILITARY RETIREE
>> NON-VETERAN (OTHER)
>> NSC VETERAN
>> SC VETERAN
>> TRICARE
>>
>> PATIENT TYPE: NON-VETERAN (OTHER)
>> PATIENT VETERAN (Y/N)?: N NO
>> PATIENT SERVICE CONNECTED?: N NO
>> PATIENT MULTIPLE BIRTH INDICATOR: N NO
>>
>> ...searching for potential duplicates
>>
>> No potential duplicates have been identified.
>>
>> ...adding new patient...new patient added
>>
>> Patient name components--
>> FAMILY (LAST) NAME: ZZTEST//
>> GIVEN (FIRST) NAME: ONE//
>> MIDDLE NAME:
>> PREFIX:
>> SUFFIX:
>> DEGREE:
>> Press ENTER to continue
>>
>> Please verify or update the following information:
>>
>> MOTHER'S MAIDEN NAME: DUCK
>> PLACE OF BIRTH [CITY]: SAN ANTONIO
>> PLACE OF BIRTH [STATE]: TEXAS
>> Select ALIAS:
>>
>> Attempting to connect to the Master Patient Index in Austin...
>> If no SSN or inexact DOB or common name, this request
>> may take some time, please be patient...
>>
>>
>> Could not connect to MPI or Timed Out, assigning local ICN (if not already assig
>> ned)...
>> %GTM-E-UNDEF, Undefined local variable: Y(0)
> --
> Full post: http://www.osehra.org/discussion/problem-while-connecting-master-patient...
> Manage my subscriptions: http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post: http://www.osehra.org/og_mailinglist/unsubscribe/603

like0

problem while connecting Master Patient Index

conor dowling's picture

p.s. the reports are:
- http://www.osehra.org/wiki/vista-analytics-foia-vs-other-vistas ...
overall difference between VistAs
- http://www.caregraf.org/fmql/reports/packagesFOIAvsWVFOAnalytics.html ...
changes World Vista has made to run outside the VA (and more)
- http://www.caregraf.org/fmql/reports/registrationForksWV.html[specifically
the registration changes]

You want the last one: that lists the changes to Registration.

On Tue, Mar 6, 2012 at 12:34 PM, Conor Dowling
<conor-dowling@caregraf.com>wrote:

> Jignesh
>
> Both world and openvista comment out or change a bunch of registration
> logic - one item is this MPI call. If you look at the registration package
> analysis in vista analytics, it lists the changes. We are going to talk
> about them into tomorrows tools call
>
> Sent from my iPhone
>
> On Mar 6, 2012, at 12:10 PM, Jignesh Patel <jigneshmpatel@gmail.com>
> wrote:
>
> While using FOIA-VistA got following error. Do we have to different setup
> for MPI connection?
>
>
> Select PATIENT NAME: ZZTEST, ONE
> ARE YOU ADDING 'ZZTEST,ONE' AS A NEW PATIENT (THE 2ND)? No// Y (Yes)
> PATIENT SEX: F FEMALE
> PATIENT DATE OF BIRTH: 341960 ??
> DOB
> Enter the patient's DATE OF BIRTH which must be later than
> 12/31/1870. DAT
> E OF BIRTH cannot be a date after the beneficiary 'Ineligible Date' or a
> date af
> ter the 'Enrollment Application Date'.
> Examples of Valid Dates:
> JAN 20 1957 or 20 JAN 57 or 1/20/57 or 012057
> T (for TODAY), T+1 (for TOMORROW), T+2, T+7, etc.
> T-1 (for YESTERDAY), T-3W (for 3 WEEKS AGO), etc.
> If the year is omitted, the computer uses CURRENT YEAR. Two digit
> year
> assumes no more than 20 years in the future, or 80 years in the
> past.
> You may omit the precise day, as: JAN, 1957
> PATIENT DATE OF BIRTH: 03041960 (MAR 04, 1960)
> PATIENT SOCIAL SECURITY NUMBER: 56544445656 ??
> SSN
> Enter 9-digit SSN or 'P' for pseudo-SSN.
> PATIENT SOCIAL SECURITY NUMBER: 565445678
> PATIENT TYPE: ?
> Choose from the available listing the PATIENT TYPE which best
> classifies th
> is patient.
> Enter the patient type for this patient. This is selectable from the
> distributed entries in the TYPE OF PATIENT file. The type selected
> should
> be the primary one selectable. For example, if the patient is both an
> ...
> Answer with TYPE OF PATIENT NAME
> Choose from:
> ACTIVE DUTY
> ALLIED VETERAN
> COLLATERAL
> EMPLOYEE
> MILITARY RETIREE
> NON-VETERAN (OTHER)
> NSC VETERAN
> SC VETERAN
> TRICARE
>
> PATIENT TYPE: NON-VETERAN (OTHER)
> PATIENT VETERAN (Y/N)?: N NO
> PATIENT SERVICE CONNECTED?: N NO
> PATIENT MULTIPLE BIRTH INDICATOR: N NO
>
> ...searching for potential duplicates
>
> No potential duplicates have been identified.
>
> ...adding new patient...new patient added
>
> Patient name components--
> FAMILY (LAST) NAME: ZZTEST//
> GIVEN (FIRST) NAME: ONE//
> MIDDLE NAME:
> PREFIX:
> SUFFIX:
> DEGREE:
> Press ENTER to continue
>
> Please verify or update the following information:
>
> MOTHER'S MAIDEN NAME: DUCK
> PLACE OF BIRTH [CITY]: SAN ANTONIO
> PLACE OF BIRTH [STATE]: TEXAS
> Select ALIAS:
>
> *Attempting to connect to the Master Patient Index in Austin...*
> *If no SSN or inexact DOB or common name, this request*
> *may take some time, please be patient...*
> *
> *
> *
> *
> *Could not connect to MPI or Timed Out, assigning local ICN (if not
> already assig*
> *ned)...*
> *%GTM-E-UNDEF, Undefined local variable: Y(0)*
>
> --
> Full post:
> http://www.osehra.org/discussion/problem-while-connecting-master-patient...
> Manage my subscriptions:
> http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post:
> http://www.osehra.org/og_mailinglist/unsubscribe/603
>
>

like0

problem while connecting Master Patient Index

Jignesh Patel's picture

Thanks Conor,
For the prompt response. We are using FOIA-VistA -so how do we integrate
MPI?

-Jignesh

On Tue, Mar 6, 2012 at 3:34 PM, Conor Dowling <conor-dowling@caregraf.com>wrote:

> Jignesh
>
> Both world and openvista comment out or change a bunch of registration
> logic - one item is this MPI call. If you look at the registration package
> analysis in vista analytics, it lists the changes. We are going to talk
> about them into tomorrows tools call
>
> Sent from my iPhone
>
> On Mar 6, 2012, at 12:10 PM, Jignesh Patel <jigneshmpatel@gmail.com>
> wrote:
>
> While using FOIA-VistA got following error. Do we have to different setup
> for MPI connection?
>
>
> Select PATIENT NAME: ZZTEST, ONE
> ARE YOU ADDING 'ZZTEST,ONE' AS A NEW PATIENT (THE 2ND)? No// Y (Yes)
> PATIENT SEX: F FEMALE
> PATIENT DATE OF BIRTH: 341960 ??
> DOB
> Enter the patient's DATE OF BIRTH which must be later than
> 12/31/1870. DAT
> E OF BIRTH cannot be a date after the beneficiary 'Ineligible Date' or a
> date af
> ter the 'Enrollment Application Date'.
> Examples of Valid Dates:
> JAN 20 1957 or 20 JAN 57 or 1/20/57 or 012057
> T (for TODAY), T+1 (for TOMORROW), T+2, T+7, etc.
> T-1 (for YESTERDAY), T-3W (for 3 WEEKS AGO), etc.
> If the year is omitted, the computer uses CURRENT YEAR. Two digit
> year
> assumes no more than 20 years in the future, or 80 years in the
> past.
> You may omit the precise day, as: JAN, 1957
> PATIENT DATE OF BIRTH: 03041960 (MAR 04, 1960)
> PATIENT SOCIAL SECURITY NUMBER: 56544445656 ??
> SSN
> Enter 9-digit SSN or 'P' for pseudo-SSN.
> PATIENT SOCIAL SECURITY NUMBER: 565445678
> PATIENT TYPE: ?
> Choose from the available listing the PATIENT TYPE which best
> classifies th
> is patient.
> Enter the patient type for this patient. This is selectable from the
> distributed entries in the TYPE OF PATIENT file. The type selected
> should
> be the primary one selectable. For example, if the patient is both an
> ...
> Answer with TYPE OF PATIENT NAME
> Choose from:
> ACTIVE DUTY
> ALLIED VETERAN
> COLLATERAL
> EMPLOYEE
> MILITARY RETIREE
> NON-VETERAN (OTHER)
> NSC VETERAN
> SC VETERAN
> TRICARE
>
> PATIENT TYPE: NON-VETERAN (OTHER)
> PATIENT VETERAN (Y/N)?: N NO
> PATIENT SERVICE CONNECTED?: N NO
> PATIENT MULTIPLE BIRTH INDICATOR: N NO
>
> ...searching for potential duplicates
>
> No potential duplicates have been identified.
>
> ...adding new patient...new patient added
>
> Patient name components--
> FAMILY (LAST) NAME: ZZTEST//
> GIVEN (FIRST) NAME: ONE//
> MIDDLE NAME:
> PREFIX:
> SUFFIX:
> DEGREE:
> Press ENTER to continue
>
> Please verify or update the following information:
>
> MOTHER'S MAIDEN NAME: DUCK
> PLACE OF BIRTH [CITY]: SAN ANTONIO
> PLACE OF BIRTH [STATE]: TEXAS
> Select ALIAS:
>
> *Attempting to connect to the Master Patient Index in Austin...*
> *If no SSN or inexact DOB or common name, this request*
> *may take some time, please be patient...*
> *
> *
> *
> *
> *Could not connect to MPI or Timed Out, assigning local ICN (if not
> already assig*
> *ned)...*
> *%GTM-E-UNDEF, Undefined local variable: Y(0)*
>
> --
> Full post:
> http://www.osehra.org/discussion/problem-while-connecting-master-patient...
> Manage my subscriptions:
> http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post:
> http://www.osehra.org/og_mailinglist/unsubscribe/603
>
>

like0

problem while connecting Master Patient Index

conor dowling's picture

Jignesh,

implementing a VA-style MPI is not worth the trouble: you'd have to write a
bunch of non-standard HL7 handling and this VistA-MPI interaction is NOT
well-documented.

Just do what WorldVistA and VxVistA did - stop the MPI call execution
before there's a call to Austin.

See: mpiForksWV <http://www.caregraf.org/fmql/reports/mpiForksWV.html>

See the second file, MPIFQ0: VxVistA just exits from "VTQ" - WV is more
nuanced and checks if a VistA is a VA or outside VistA. The first change is
easiest; the second, more proper. Either way, you have to change FOIA's
MPIFQ0 to avoid the MPI call. Changes like this are being discussed on
tomorrow's call.

Conor

p.s. Luis - for tomorrows call, I think that the MPI and Registration
changes should be taken together.

p.p.s. I updated the OSEHRA wiki for
Analytics<http://www.osehra.org/wiki/vista-analytics-foia-vs-other-vistas>to
refer to the Registration and MPI diff reports.

On Tue, Mar 6, 2012 at 1:16 PM, Jignesh Patel <jigneshmpatel@gmail.com>wrote:

> Thanks Conor,
> For the prompt response. We are using FOIA-VistA -so how do we integrate
> MPI?
>
> -Jignesh
>
> On Tue, Mar 6, 2012 at 3:34 PM, Conor Dowling <conor-dowling@caregraf.com>wrote:
>
>> Jignesh
>>
>> Both world and openvista comment out or change a bunch of registration
>> logic - one item is this MPI call. If you look at the registration package
>> analysis in vista analytics, it lists the changes. We are going to talk
>> about them into tomorrows tools call
>>
>> Sent from my iPhone
>>
>> On Mar 6, 2012, at 12:10 PM, Jignesh Patel <jigneshmpatel@gmail.com>
>> wrote:
>>
>> While using FOIA-VistA got following error. Do we have to different setup
>> for MPI connection?
>>
>>
>> Select PATIENT NAME: ZZTEST, ONE
>> ARE YOU ADDING 'ZZTEST,ONE' AS A NEW PATIENT (THE 2ND)? No// Y (Yes)
>> PATIENT SEX: F FEMALE
>> PATIENT DATE OF BIRTH: 341960 ??
>> DOB
>> Enter the patient's DATE OF BIRTH which must be later than
>> 12/31/1870. DAT
>> E OF BIRTH cannot be a date after the beneficiary 'Ineligible Date' or a
>> date af
>> ter the 'Enrollment Application Date'.
>> Examples of Valid Dates:
>> JAN 20 1957 or 20 JAN 57 or 1/20/57 or 012057
>> T (for TODAY), T+1 (for TOMORROW), T+2, T+7, etc.
>> T-1 (for YESTERDAY), T-3W (for 3 WEEKS AGO), etc.
>> If the year is omitted, the computer uses CURRENT YEAR. Two digit
>> year
>> assumes no more than 20 years in the future, or 80 years in the
>> past.
>> You may omit the precise day, as: JAN, 1957
>> PATIENT DATE OF BIRTH: 03041960 (MAR 04, 1960)
>> PATIENT SOCIAL SECURITY NUMBER: 56544445656 ??
>> SSN
>> Enter 9-digit SSN or 'P' for pseudo-SSN.
>> PATIENT SOCIAL SECURITY NUMBER: 565445678
>> PATIENT TYPE: ?
>> Choose from the available listing the PATIENT TYPE which best
>> classifies th
>> is patient.
>> Enter the patient type for this patient. This is selectable from the
>> distributed entries in the TYPE OF PATIENT file. The type selected
>> should
>> be the primary one selectable. For example, if the patient is both
>> an
>> ...
>> Answer with TYPE OF PATIENT NAME
>> Choose from:
>> ACTIVE DUTY
>> ALLIED VETERAN
>> COLLATERAL
>> EMPLOYEE
>> MILITARY RETIREE
>> NON-VETERAN (OTHER)
>> NSC VETERAN
>> SC VETERAN
>> TRICARE
>>
>> PATIENT TYPE: NON-VETERAN (OTHER)
>> PATIENT VETERAN (Y/N)?: N NO
>> PATIENT SERVICE CONNECTED?: N NO
>> PATIENT MULTIPLE BIRTH INDICATOR: N NO
>>
>> ...searching for potential duplicates
>>
>> No potential duplicates have been identified.
>>
>> ...adding new patient...new patient added
>>
>> Patient name components--
>> FAMILY (LAST) NAME: ZZTEST//
>> GIVEN (FIRST) NAME: ONE//
>> MIDDLE NAME:
>> PREFIX:
>> SUFFIX:
>> DEGREE:
>> Press ENTER to continue
>>
>> Please verify or update the following information:
>>
>> MOTHER'S MAIDEN NAME: DUCK
>> PLACE OF BIRTH [CITY]: SAN ANTONIO
>> PLACE OF BIRTH [STATE]: TEXAS
>> Select ALIAS:
>>
>> *Attempting to connect to the Master Patient Index in Austin...*
>> *If no SSN or inexact DOB or common name, this request*
>> *may take some time, please be patient...*
>> *
>> *
>> *
>> *
>> *Could not connect to MPI or Timed Out, assigning local ICN (if not
>> already assig*
>> *ned)...*
>> *%GTM-E-UNDEF, Undefined local variable: Y(0)*
>>
>> --
>> Full post:
>> http://www.osehra.org/discussion/problem-while-connecting-master-patient...
>> Manage my subscriptions:
>> http://www.osehra.org/og_mailinglist/subscriptions
>> Stop emails for this post:
>> http://www.osehra.org/og_mailinglist/unsubscribe/603
>>
>>
>

like0

problem while connecting Master Patient Index

Jignesh Patel's picture

Conor,
Just curious, by replacing MPIFQ0.m with WorldVIstA verson can solve the
probem?

-Jignesh
On Tue, Mar 6, 2012 at 8:55 PM, Conor Dowling <conor-dowling@caregraf.com>wrote:

> Jignesh,
>
> implementing a VA-style MPI is not worth the trouble: you'd have to write
> a bunch of non-standard HL7 handling and this VistA-MPI interaction is NOT
> well-documented.
>
> Just do what WorldVistA and VxVistA did - stop the MPI call execution
> before there's a call to Austin.
>
> See: mpiForksWV <http://www.caregraf.org/fmql/reports/mpiForksWV.html>
>
> See the second file, MPIFQ0: VxVistA just exits from "VTQ" - WV is more
> nuanced and checks if a VistA is a VA or outside VistA. The first change is
> easiest; the second, more proper. Either way, you have to change FOIA's
> MPIFQ0 to avoid the MPI call. Changes like this are being discussed on
> tomorrow's call.
>
> Conor
>
> p.s. Luis - for tomorrows call, I think that the MPI and Registration
> changes should be taken together.
>
> p.p.s. I updated the OSEHRA wiki for Analytics<http://www.osehra.org/wiki/vista-analytics-foia-vs-other-vistas>to refer to the Registration and MPI diff reports.
>
> On Tue, Mar 6, 2012 at 1:16 PM, Jignesh Patel <jigneshmpatel@gmail.com>wrote:
>
>> Thanks Conor,
>> For the prompt response. We are using FOIA-VistA -so how do we integrate
>> MPI?
>>
>> -Jignesh
>>
>> On Tue, Mar 6, 2012 at 3:34 PM, Conor Dowling <conor-dowling@caregraf.com
>> > wrote:
>>
>>> Jignesh
>>>
>>> Both world and openvista comment out or change a bunch of registration
>>> logic - one item is this MPI call. If you look at the registration package
>>> analysis in vista analytics, it lists the changes. We are going to talk
>>> about them into tomorrows tools call
>>>
>>> Sent from my iPhone
>>>
>>> On Mar 6, 2012, at 12:10 PM, Jignesh Patel <jigneshmpatel@gmail.com>
>>> wrote:
>>>
>>> While using FOIA-VistA got following error. Do we have to different
>>> setup for MPI connection?
>>>
>>>
>>> Select PATIENT NAME: ZZTEST, ONE
>>> ARE YOU ADDING 'ZZTEST,ONE' AS A NEW PATIENT (THE 2ND)? No// Y (Yes)
>>> PATIENT SEX: F FEMALE
>>> PATIENT DATE OF BIRTH: 341960 ??
>>> DOB
>>> Enter the patient's DATE OF BIRTH which must be later than
>>> 12/31/1870. DAT
>>> E OF BIRTH cannot be a date after the beneficiary 'Ineligible Date' or a
>>> date af
>>> ter the 'Enrollment Application Date'.
>>> Examples of Valid Dates:
>>> JAN 20 1957 or 20 JAN 57 or 1/20/57 or 012057
>>> T (for TODAY), T+1 (for TOMORROW), T+2, T+7, etc.
>>> T-1 (for YESTERDAY), T-3W (for 3 WEEKS AGO), etc.
>>> If the year is omitted, the computer uses CURRENT YEAR. Two digit
>>> year
>>> assumes no more than 20 years in the future, or 80 years in the
>>> past.
>>> You may omit the precise day, as: JAN, 1957
>>> PATIENT DATE OF BIRTH: 03041960 (MAR 04, 1960)
>>> PATIENT SOCIAL SECURITY NUMBER: 56544445656 ??
>>> SSN
>>> Enter 9-digit SSN or 'P' for pseudo-SSN.
>>> PATIENT SOCIAL SECURITY NUMBER: 565445678
>>> PATIENT TYPE: ?
>>> Choose from the available listing the PATIENT TYPE which best
>>> classifies th
>>> is patient.
>>> Enter the patient type for this patient. This is selectable from
>>> the
>>> distributed entries in the TYPE OF PATIENT file. The type selected
>>> should
>>> be the primary one selectable. For example, if the patient is both
>>> an
>>> ...
>>> Answer with TYPE OF PATIENT NAME
>>> Choose from:
>>> ACTIVE DUTY
>>> ALLIED VETERAN
>>> COLLATERAL
>>> EMPLOYEE
>>> MILITARY RETIREE
>>> NON-VETERAN (OTHER)
>>> NSC VETERAN
>>> SC VETERAN
>>> TRICARE
>>>
>>> PATIENT TYPE: NON-VETERAN (OTHER)
>>> PATIENT VETERAN (Y/N)?: N NO
>>> PATIENT SERVICE CONNECTED?: N NO
>>> PATIENT MULTIPLE BIRTH INDICATOR: N NO
>>>
>>> ...searching for potential duplicates
>>>
>>> No potential duplicates have been identified.
>>>
>>> ...adding new patient...new patient added
>>>
>>> Patient name components--
>>> FAMILY (LAST) NAME: ZZTEST//
>>> GIVEN (FIRST) NAME: ONE//
>>> MIDDLE NAME:
>>> PREFIX:
>>> SUFFIX:
>>> DEGREE:
>>> Press ENTER to continue
>>>
>>> Please verify or update the following information:
>>>
>>> MOTHER'S MAIDEN NAME: DUCK
>>> PLACE OF BIRTH [CITY]: SAN ANTONIO
>>> PLACE OF BIRTH [STATE]: TEXAS
>>> Select ALIAS:
>>>
>>> *Attempting to connect to the Master Patient Index in Austin...*
>>> *If no SSN or inexact DOB or common name, this request*
>>> *may take some time, please be patient...*
>>> *
>>> *
>>> *
>>> *
>>> *Could not connect to MPI or Timed Out, assigning local ICN (if not
>>> already assig*
>>> *ned)...*
>>> *%GTM-E-UNDEF, Undefined local variable: Y(0)*
>>>
>>> --
>>> Full post:
>>> http://www.osehra.org/discussion/problem-while-connecting-master-patient...
>>> Manage my subscriptions:
>>> http://www.osehra.org/og_mailinglist/subscriptions
>>> Stop emails for this post:
>>> http://www.osehra.org/og_mailinglist/unsubscribe/603
>>>
>>>
>>
>

like0

problem while connecting Master Patient Index

Jignesh Patel's picture

I have replaced MPIFQ0.m of FOIA-VistA with world vista and after
compilation, even after object file created I still see following error:

Attempting to connect to the Master Patient Index in Austin...
If no SSN or inexact DOB or common name, this request
may take some time, please be patient...

Could not connect to MPI or Timed Out, assigning local ICN (if not already
assig
ned)...

Do I need to do anything else to get it work.

-Jignesh

>
> On Tue, Mar 6, 2012 at 8:55 PM, Conor Dowling <conor-dowling@caregraf.com>wrote:
>
>> Jignesh,
>>
>> implementing a VA-style MPI is not worth the trouble: you'd have to write
>> a bunch of non-standard HL7 handling and this VistA-MPI interaction is NOT
>> well-documented.
>>
>> Just do what WorldVistA and VxVistA did - stop the MPI call execution
>> before there's a call to Austin.
>>
>> See: mpiForksWV <http://www.caregraf.org/fmql/reports/mpiForksWV.html>
>>
>> See the second file, MPIFQ0: VxVistA just exits from "VTQ" - WV is more
>> nuanced and checks if a VistA is a VA or outside VistA. The first change is
>> easiest; the second, more proper. Either way, you have to change FOIA's
>> MPIFQ0 to avoid the MPI call. Changes like this are being discussed on
>> tomorrow's call.
>>
>> Conor
>>
>> p.s. Luis - for tomorrows call, I think that the MPI and Registration
>> changes should be taken together.
>>
>> p.p.s. I updated the OSEHRA wiki for Analytics<http://www.osehra.org/wiki/vista-analytics-foia-vs-other-vistas>to refer to the Registration and MPI diff reports.
>>
>> On Tue, Mar 6, 2012 at 1:16 PM, Jignesh Patel <jigneshmpatel@gmail.com>wrote:
>>
>>> Thanks Conor,
>>> For the prompt response. We are using FOIA-VistA -so how do we integrate
>>> MPI?
>>>
>>> -Jignesh
>>>
>>> On Tue, Mar 6, 2012 at 3:34 PM, Conor Dowling <
>>> conor-dowling@caregraf.com> wrote:
>>>
>>>> Jignesh
>>>>
>>>> Both world and openvista comment out or change a bunch of registration
>>>> logic - one item is this MPI call. If you look at the registration package
>>>> analysis in vista analytics, it lists the changes. We are going to talk
>>>> about them into tomorrows tools call
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On Mar 6, 2012, at 12:10 PM, Jignesh Patel <jigneshmpatel@gmail.com>
>>>> wrote:
>>>>
>>>> While using FOIA-VistA got following error. Do we have to different
>>>> setup for MPI connection?
>>>>
>>>>
>>>> Select PATIENT NAME: ZZTEST, ONE
>>>> ARE YOU ADDING 'ZZTEST,ONE' AS A NEW PATIENT (THE 2ND)? No// Y (Yes)
>>>> PATIENT SEX: F FEMALE
>>>> PATIENT DATE OF BIRTH: 341960 ??
>>>> DOB
>>>> Enter the patient's DATE OF BIRTH which must be later than
>>>> 12/31/1870. DAT
>>>> E OF BIRTH cannot be a date after the beneficiary 'Ineligible Date' or
>>>> a date af
>>>> ter the 'Enrollment Application Date'.
>>>> Examples of Valid Dates:
>>>> JAN 20 1957 or 20 JAN 57 or 1/20/57 or 012057
>>>> T (for TODAY), T+1 (for TOMORROW), T+2, T+7, etc.
>>>> T-1 (for YESTERDAY), T-3W (for 3 WEEKS AGO), etc.
>>>> If the year is omitted, the computer uses CURRENT YEAR. Two digit
>>>> year
>>>> assumes no more than 20 years in the future, or 80 years in the
>>>> past.
>>>> You may omit the precise day, as: JAN, 1957
>>>> PATIENT DATE OF BIRTH: 03041960 (MAR 04, 1960)
>>>> PATIENT SOCIAL SECURITY NUMBER: 56544445656 ??
>>>> SSN
>>>> Enter 9-digit SSN or 'P' for pseudo-SSN.
>>>> PATIENT SOCIAL SECURITY NUMBER: 565445678
>>>> PATIENT TYPE: ?
>>>> Choose from the available listing the PATIENT TYPE which best
>>>> classifies th
>>>> is patient.
>>>> Enter the patient type for this patient. This is selectable from
>>>> the
>>>> distributed entries in the TYPE OF PATIENT file. The type
>>>> selected should
>>>> be the primary one selectable. For example, if the patient is
>>>> both an
>>>> ...
>>>> Answer with TYPE OF PATIENT NAME
>>>> Choose from:
>>>> ACTIVE DUTY
>>>> ALLIED VETERAN
>>>> COLLATERAL
>>>> EMPLOYEE
>>>> MILITARY RETIREE
>>>> NON-VETERAN (OTHER)
>>>> NSC VETERAN
>>>> SC VETERAN
>>>> TRICARE
>>>>
>>>> PATIENT TYPE: NON-VETERAN (OTHER)
>>>> PATIENT VETERAN (Y/N)?: N NO
>>>> PATIENT SERVICE CONNECTED?: N NO
>>>> PATIENT MULTIPLE BIRTH INDICATOR: N NO
>>>>
>>>> ...searching for potential duplicates
>>>>
>>>> No potential duplicates have been identified.
>>>>
>>>> ...adding new patient...new patient added
>>>>
>>>> Patient name components--
>>>> FAMILY (LAST) NAME: ZZTEST//
>>>> GIVEN (FIRST) NAME: ONE//
>>>> MIDDLE NAME:
>>>> PREFIX:
>>>> SUFFIX:
>>>> DEGREE:
>>>> Press ENTER to continue
>>>>
>>>> Please verify or update the following information:
>>>>
>>>> MOTHER'S MAIDEN NAME: DUCK
>>>> PLACE OF BIRTH [CITY]: SAN ANTONIO
>>>> PLACE OF BIRTH [STATE]: TEXAS
>>>> Select ALIAS:
>>>>
>>>> *Attempting to connect to the Master Patient Index in Austin...*
>>>> *If no SSN or inexact DOB or common name, this request*
>>>> *may take some time, please be patient...*
>>>> *
>>>> *
>>>> *
>>>> *
>>>> *Could not connect to MPI or Timed Out, assigning local ICN (if not
>>>> already assig*
>>>> *ned)...*
>>>> *%GTM-E-UNDEF, Undefined local variable: Y(0)*
>>>>
>>>> --
>>>> Full post:
>>>> http://www.osehra.org/discussion/problem-while-connecting-master-patient...
>>>> Manage my subscriptions:
>>>> http://www.osehra.org/og_mailinglist/subscriptions
>>>> Stop emails for this post:
>>>> http://www.osehra.org/og_mailinglist/unsubscribe/603
>>>>
>>>>
>>>
>>
>

like0

problem while connecting Master Patient Index

conor dowling's picture

Jignesh,

for now, use VxVistA's version. It exits the MPI pass unconditionally - you
don't need any of WV's environment settings. So that should work to stop
MPI invocation.

Conor

On Mon, Mar 12, 2012 at 11:08 AM, Jignesh Patel <jigneshmpatel@gmail.com>wrote:

> I have replaced MPIFQ0.m of FOIA-VistA with world vista and after
> compilation, even after object file created I still see following error:
>
>
> Attempting to connect to the Master Patient Index in Austin...
> If no SSN or inexact DOB or common name, this request
> may take some time, please be patient...
>
>
> Could not connect to MPI or Timed Out, assigning local ICN (if not already
> assig
> ned)...
>
> Do I need to do anything else to get it work.
>
> -Jignesh
>
>>
>> On Tue, Mar 6, 2012 at 8:55 PM, Conor Dowling <conor-dowling@caregraf.com
>> > wrote:
>>
>>> Jignesh,
>>>
>>> implementing a VA-style MPI is not worth the trouble: you'd have to
>>> write a bunch of non-standard HL7 handling and this VistA-MPI interaction
>>> is NOT well-documented.
>>>
>>> Just do what WorldVistA and VxVistA did - stop the MPI call execution
>>> before there's a call to Austin.
>>>
>>> See: mpiForksWV <http://www.caregraf.org/fmql/reports/mpiForksWV.html>
>>>
>>> See the second file, MPIFQ0: VxVistA just exits from "VTQ" - WV is more
>>> nuanced and checks if a VistA is a VA or outside VistA. The first change is
>>> easiest; the second, more proper. Either way, you have to change FOIA's
>>> MPIFQ0 to avoid the MPI call. Changes like this are being discussed on
>>> tomorrow's call.
>>>
>>> Conor
>>>
>>> p.s. Luis - for tomorrows call, I think that the MPI and Registration
>>> changes should be taken together.
>>>
>>> p.p.s. I updated the OSEHRA wiki for Analytics<http://www.osehra.org/wiki/vista-analytics-foia-vs-other-vistas>to refer to the Registration and MPI diff reports.
>>>
>>> On Tue, Mar 6, 2012 at 1:16 PM, Jignesh Patel <jigneshmpatel@gmail.com>wrote:
>>>
>>>> Thanks Conor,
>>>> For the prompt response. We are using FOIA-VistA -so how do we
>>>> integrate MPI?
>>>>
>>>> -Jignesh
>>>>
>>>> On Tue, Mar 6, 2012 at 3:34 PM, Conor Dowling <
>>>> conor-dowling@caregraf.com> wrote:
>>>>
>>>>> Jignesh
>>>>>
>>>>> Both world and openvista comment out or change a bunch of registration
>>>>> logic - one item is this MPI call. If you look at the registration package
>>>>> analysis in vista analytics, it lists the changes. We are going to talk
>>>>> about them into tomorrows tools call
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On Mar 6, 2012, at 12:10 PM, Jignesh Patel <jigneshmpatel@gmail.com>
>>>>> wrote:
>>>>>
>>>>> While using FOIA-VistA got following error. Do we have to different
>>>>> setup for MPI connection?
>>>>>
>>>>>
>>>>> Select PATIENT NAME: ZZTEST, ONE
>>>>> ARE YOU ADDING 'ZZTEST,ONE' AS A NEW PATIENT (THE 2ND)? No// Y
>>>>> (Yes)
>>>>> PATIENT SEX: F FEMALE
>>>>> PATIENT DATE OF BIRTH: 341960 ??
>>>>> DOB
>>>>> Enter the patient's DATE OF BIRTH which must be later than
>>>>> 12/31/1870. DAT
>>>>> E OF BIRTH cannot be a date after the beneficiary 'Ineligible Date' or
>>>>> a date af
>>>>> ter the 'Enrollment Application Date'.
>>>>> Examples of Valid Dates:
>>>>> JAN 20 1957 or 20 JAN 57 or 1/20/57 or 012057
>>>>> T (for TODAY), T+1 (for TOMORROW), T+2, T+7, etc.
>>>>> T-1 (for YESTERDAY), T-3W (for 3 WEEKS AGO), etc.
>>>>> If the year is omitted, the computer uses CURRENT YEAR. Two
>>>>> digit year
>>>>> assumes no more than 20 years in the future, or 80 years in the
>>>>> past.
>>>>> You may omit the precise day, as: JAN, 1957
>>>>> PATIENT DATE OF BIRTH: 03041960 (MAR 04, 1960)
>>>>> PATIENT SOCIAL SECURITY NUMBER: 56544445656 ??
>>>>> SSN
>>>>> Enter 9-digit SSN or 'P' for pseudo-SSN.
>>>>> PATIENT SOCIAL SECURITY NUMBER: 565445678
>>>>> PATIENT TYPE: ?
>>>>> Choose from the available listing the PATIENT TYPE which best
>>>>> classifies th
>>>>> is patient.
>>>>> Enter the patient type for this patient. This is selectable from
>>>>> the
>>>>> distributed entries in the TYPE OF PATIENT file. The type
>>>>> selected should
>>>>> be the primary one selectable. For example, if the patient is
>>>>> both an
>>>>> ...
>>>>> Answer with TYPE OF PATIENT NAME
>>>>> Choose from:
>>>>> ACTIVE DUTY
>>>>> ALLIED VETERAN
>>>>> COLLATERAL
>>>>> EMPLOYEE
>>>>> MILITARY RETIREE
>>>>> NON-VETERAN (OTHER)
>>>>> NSC VETERAN
>>>>> SC VETERAN
>>>>> TRICARE
>>>>>
>>>>> PATIENT TYPE: NON-VETERAN (OTHER)
>>>>> PATIENT VETERAN (Y/N)?: N NO
>>>>> PATIENT SERVICE CONNECTED?: N NO
>>>>> PATIENT MULTIPLE BIRTH INDICATOR: N NO
>>>>>
>>>>> ...searching for potential duplicates
>>>>>
>>>>> No potential duplicates have been identified.
>>>>>
>>>>> ...adding new patient...new patient added
>>>>>
>>>>> Patient name components--
>>>>> FAMILY (LAST) NAME: ZZTEST//
>>>>> GIVEN (FIRST) NAME: ONE//
>>>>> MIDDLE NAME:
>>>>> PREFIX:
>>>>> SUFFIX:
>>>>> DEGREE:
>>>>> Press ENTER to continue
>>>>>
>>>>> Please verify or update the following information:
>>>>>
>>>>> MOTHER'S MAIDEN NAME: DUCK
>>>>> PLACE OF BIRTH [CITY]: SAN ANTONIO
>>>>> PLACE OF BIRTH [STATE]: TEXAS
>>>>> Select ALIAS:
>>>>>
>>>>> *Attempting to connect to the Master Patient Index in Austin...*
>>>>> *If no SSN or inexact DOB or common name, this request*
>>>>> *may take some time, please be patient...*
>>>>> *
>>>>> *
>>>>> *
>>>>> *
>>>>> *Could not connect to MPI or Timed Out, assigning local ICN (if not
>>>>> already assig*
>>>>> *ned)...*
>>>>> *%GTM-E-UNDEF, Undefined local variable: Y(0)*
>>>>>
>>>>> --
>>>>> Full post:
>>>>> http://www.osehra.org/discussion/problem-while-connecting-master-patient...
>>>>> Manage my subscriptions:
>>>>> http://www.osehra.org/og_mailinglist/subscriptions
>>>>> Stop emails for this post:
>>>>> http://www.osehra.org/og_mailinglist/unsubscribe/603
>>>>>
>>>>>
>>>>
>>>
>>
>

like0

problem while connecting Master Patient Index

Jignesh Patel's picture

Conor,

I have manually added following code
G EXIT

however it doesn't solve my whole problem.

So best option to replace whole routine. Now when I tried to download
VxVIstA it has only cache a version. SOmehow I have downloaded routines
from
http://www.seaislandsystems.com/vxVistA/vxVistA.tar.gz

But it is missing MPIFQ0.m routine.

-Jignesh

On Mon, Mar 12, 2012 at 2:12 PM, Conor Dowling
<conor-dowling@caregraf.com>wrote:

> Jignesh,
>
> for now, use VxVistA's version. It exits the MPI pass unconditionally -
> you don't need any of WV's environment settings. So that should work to
> stop MPI invocation.
>
> Conor
>
> On Mon, Mar 12, 2012 at 11:08 AM, Jignesh Patel <jigneshmpatel@gmail.com>wrote:
>
>> I have replaced MPIFQ0.m of FOIA-VistA with world vista and after
>> compilation, even after object file created I still see following error:
>>
>>
>> Attempting to connect to the Master Patient Index in Austin...
>> If no SSN or inexact DOB or common name, this request
>> may take some time, please be patient...
>>
>>
>> Could not connect to MPI or Timed Out, assigning local ICN (if not
>> already assig
>> ned)...
>>
>> Do I need to do anything else to get it work.
>>
>> -Jignesh
>>
>>>
>>> On Tue, Mar 6, 2012 at 8:55 PM, Conor Dowling <
>>> conor-dowling@caregraf.com> wrote:
>>>
>>>> Jignesh,
>>>>
>>>> implementing a VA-style MPI is not worth the trouble: you'd have to
>>>> write a bunch of non-standard HL7 handling and this VistA-MPI interaction
>>>> is NOT well-documented.
>>>>
>>>> Just do what WorldVistA and VxVistA did - stop the MPI call execution
>>>> before there's a call to Austin.
>>>>
>>>> See: mpiForksWV <http://www.caregraf.org/fmql/reports/mpiForksWV.html>
>>>>
>>>> See the second file, MPIFQ0: VxVistA just exits from "VTQ" - WV is
>>>> more nuanced and checks if a VistA is a VA or outside VistA. The first
>>>> change is easiest; the second, more proper. Either way, you have to change
>>>> FOIA's MPIFQ0 to avoid the MPI call. Changes like this are being discussed
>>>> on tomorrow's call.
>>>>
>>>> Conor
>>>>
>>>> p.s. Luis - for tomorrows call, I think that the MPI and Registration
>>>> changes should be taken together.
>>>>
>>>> p.p.s. I updated the OSEHRA wiki for Analytics<http://www.osehra.org/wiki/vista-analytics-foia-vs-other-vistas>to refer to the Registration and MPI diff reports.
>>>>
>>>> On Tue, Mar 6, 2012 at 1:16 PM, Jignesh Patel <jigneshmpatel@gmail.com>wrote:
>>>>
>>>>> Thanks Conor,
>>>>> For the prompt response. We are using FOIA-VistA -so how do we
>>>>> integrate MPI?
>>>>>
>>>>> -Jignesh
>>>>>
>>>>> On Tue, Mar 6, 2012 at 3:34 PM, Conor Dowling <
>>>>> conor-dowling@caregraf.com> wrote:
>>>>>
>>>>>> Jignesh
>>>>>>
>>>>>> Both world and openvista comment out or change a bunch of
>>>>>> registration logic - one item is this MPI call. If you look at the
>>>>>> registration package analysis in vista analytics, it lists the changes. We
>>>>>> are going to talk about them into tomorrows tools call
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>> On Mar 6, 2012, at 12:10 PM, Jignesh Patel <jigneshmpatel@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> While using FOIA-VistA got following error. Do we have to different
>>>>>> setup for MPI connection?
>>>>>>
>>>>>>
>>>>>> Select PATIENT NAME: ZZTEST, ONE
>>>>>> ARE YOU ADDING 'ZZTEST,ONE' AS A NEW PATIENT (THE 2ND)? No// Y
>>>>>> (Yes)
>>>>>> PATIENT SEX: F FEMALE
>>>>>> PATIENT DATE OF BIRTH: 341960 ??
>>>>>> DOB
>>>>>> Enter the patient's DATE OF BIRTH which must be later than
>>>>>> 12/31/1870. DAT
>>>>>> E OF BIRTH cannot be a date after the beneficiary 'Ineligible Date'
>>>>>> or a date af
>>>>>> ter the 'Enrollment Application Date'.
>>>>>> Examples of Valid Dates:
>>>>>> JAN 20 1957 or 20 JAN 57 or 1/20/57 or 012057
>>>>>> T (for TODAY), T+1 (for TOMORROW), T+2, T+7, etc.
>>>>>> T-1 (for YESTERDAY), T-3W (for 3 WEEKS AGO), etc.
>>>>>> If the year is omitted, the computer uses CURRENT YEAR. Two
>>>>>> digit year
>>>>>> assumes no more than 20 years in the future, or 80 years in
>>>>>> the past.
>>>>>> You may omit the precise day, as: JAN, 1957
>>>>>> PATIENT DATE OF BIRTH: 03041960 (MAR 04, 1960)
>>>>>> PATIENT SOCIAL SECURITY NUMBER: 56544445656 ??
>>>>>> SSN
>>>>>> Enter 9-digit SSN or 'P' for pseudo-SSN.
>>>>>> PATIENT SOCIAL SECURITY NUMBER: 565445678
>>>>>> PATIENT TYPE: ?
>>>>>> Choose from the available listing the PATIENT TYPE which best
>>>>>> classifies th
>>>>>> is patient.
>>>>>> Enter the patient type for this patient. This is selectable
>>>>>> from the
>>>>>> distributed entries in the TYPE OF PATIENT file. The type
>>>>>> selected should
>>>>>> be the primary one selectable. For example, if the patient is
>>>>>> both an
>>>>>> ...
>>>>>> Answer with TYPE OF PATIENT NAME
>>>>>> Choose from:
>>>>>> ACTIVE DUTY
>>>>>> ALLIED VETERAN
>>>>>> COLLATERAL
>>>>>> EMPLOYEE
>>>>>> MILITARY RETIREE
>>>>>> NON-VETERAN (OTHER)
>>>>>> NSC VETERAN
>>>>>> SC VETERAN
>>>>>> TRICARE
>>>>>>
>>>>>> PATIENT TYPE: NON-VETERAN (OTHER)
>>>>>> PATIENT VETERAN (Y/N)?: N NO
>>>>>> PATIENT SERVICE CONNECTED?: N NO
>>>>>> PATIENT MULTIPLE BIRTH INDICATOR: N NO
>>>>>>
>>>>>> ...searching for potential duplicates
>>>>>>
>>>>>> No potential duplicates have been identified.
>>>>>>
>>>>>> ...adding new patient...new patient added
>>>>>>
>>>>>> Patient name components--
>>>>>> FAMILY (LAST) NAME: ZZTEST//
>>>>>> GIVEN (FIRST) NAME: ONE//
>>>>>> MIDDLE NAME:
>>>>>> PREFIX:
>>>>>> SUFFIX:
>>>>>> DEGREE:
>>>>>> Press ENTER to continue
>>>>>>
>>>>>> Please verify or update the following information:
>>>>>>
>>>>>> MOTHER'S MAIDEN NAME: DUCK
>>>>>> PLACE OF BIRTH [CITY]: SAN ANTONIO
>>>>>> PLACE OF BIRTH [STATE]: TEXAS
>>>>>> Select ALIAS:
>>>>>>
>>>>>> *Attempting to connect to the Master Patient Index in Austin...*
>>>>>> *If no SSN or inexact DOB or common name, this request*
>>>>>> *may take some time, please be patient...*
>>>>>> *
>>>>>> *
>>>>>> *
>>>>>> *
>>>>>> *Could not connect to MPI or Timed Out, assigning local ICN (if not
>>>>>> already assig*
>>>>>> *ned)...*
>>>>>> *%GTM-E-UNDEF, Undefined local variable: Y(0)*
>>>>>>
>>>>>> --
>>>>>> Full post:
>>>>>> http://www.osehra.org/discussion/problem-while-connecting-master-patient...
>>>>>> Manage my subscriptions:
>>>>>> http://www.osehra.org/og_mailinglist/subscriptions
>>>>>> Stop emails for this post:
>>>>>> http://www.osehra.org/og_mailinglist/unsubscribe/603
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

like0