Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All
Print Page as PDF
Global: ^IBA(355.3

Package: Integrated Billing

Global: ^IBA(355.3


Information

FileMan FileNo FileMan Filename Package
355.3 GROUP INSURANCE PLAN Integrated Billing

Description

Directly Accessed By Routines, Total: 27

Package Total Routines
Integrated Billing 26 IBCNS1    IBTOBI1    ^IBA(355.3    ^IBA(355.4    IB20PT1    IB20PT6    IBCNS    IBCNSA
IBCNSA0    IBCNSC3    IBCNSM    IBCNSM1    IBCNSM3    IBCNSM31    IBCNSM5    IBCNSOK
IBCNSOK1    IBCNSP    IBCNSP0    IBCNSP1    IBCNSP3    IBCNSU    IBRFN2    IBTOAT1
INSURANCE TYPE    ^DIC(36    

Accessed By FileMan Db Calls, Total: 7

Package Total Routines
Integrated Billing 7 IBCNSC3    IBCNSM1    IBCNSM3    IBCNSM31    IBCNSP1    IBCNSP3    IBCNSU    

Pointed To By FileMan Files, Total: 3

Package Total FileMan Files
Integrated Billing 2 ANNUAL BENEFITS(#355.4)[.02]    INSURANCE CLAIMS YEAR TO DATE(#355.5)[.01]    
Registration 1 VA PATIENT(#2)[#2.312(.18)]    

Pointer To FileMan Files, Total: 4

Package Total FileMan Files
Integrated Billing 2 INSURANCE COMPANY(#36)[.01]    TYPE OF PLAN(#355.1)[.09]    
Kernel 1 NEW PERSON(#200)[1.021.041.06]
Registration 1 VA PATIENT(#2)[.1]    

Fields, Total: 17

Field # Name Loc Type Details
.01 INSURANCE COMPANY 0;1 POINTER TO INSURANCE COMPANY FILE (#36)
************************REQUIRED FIELD************************
INSURANCE COMPANY(#36)

  • LAST EDITED:  FEB 13, 1994
  • DESCRIPTION:  
    Select the insurance company that this policy is with.
  • CROSS-REFERENCE:  355.3^B
    1)= S ^IBA(355.3,"B",$E(X,1,30),DA)=""
    2)= K ^IBA(355.3,"B",$E(X,1,30),DA)
  • CROSS-REFERENCE:  ^^TRIGGER^355.3^1.01
    1)= K DIV S DIV=X,D0=DA,DIV(0)=D0 S Y(0)=X S Y(1)=$S($D(^IBA(355.3,D0,1)):^(1),1:"") S X=$P(Y(1),U,1)="" I X S X=DIV S Y(1)=$S($D(^IBA(355.3,D0,1)):^(1),1:"") S X=$P(Y(1),U,1),X=X S DIU=X K Y X ^DD(355.3,.01,1,2,1.1) X ^DD
    (355.3,.01,1,2,1.4)
    1.1)= S X=DIV N %I,%H,% D NOW^%DTC S X=%
    1.4)= S DIH=$S($D(^IBA(355.3,DIV(0),1)):^(1),1:""),DIV=X S $P(^(1),U,1)=DIV,DIH=355.3,DIG=1.01 D ^DICR:$O(^DD(DIH,DIG,1,0))>0
    2)= Q
    CREATE CONDITION)= #1.01=""
    CREATE VALUE)= NOW
    DELETE VALUE)= NO EFFECT
    FIELD)= #1.01
    Triggers the date/time entered when creating a new entry.
  • CROSS-REFERENCE:  ^^TRIGGER^355.3^1.02
    1)= X ^DD(355.3,.01,1,3,1.3) I X S X=DIV S Y(1)=$S($D(^IBA(355.3,D0,1)):^(1),1:"") S X=$P(Y(1),U,2),X=X S DIU=X K Y S X=DIV S X=DUZ X ^DD(355.3,.01,1,3,1.4)
    1.3)= K DIV S DIV=X,D0=DA,DIV(0)=D0 S Y(0)=X S Y(1)=$S($D(^IBA(355.3,D0,1)):^(1),1:"") S X=$S('$D(^VA(200,+$P(Y(1),U,2),0)):"",1:$P(^(0),U,1))=""
    1.4)= S DIH=$S($D(^IBA(355.3,DIV(0),1)):^(1),1:""),DIV=X S $P(^(1),U,2)=DIV,DIH=355.3,DIG=1.02 D ^DICR:$O(^DD(DIH,DIG,1,0))>0
    2)= Q
    CREATE CONDITION)= #1.02=""
    CREATE VALUE)= S X=DUZ
    DELETE VALUE)= NO EFFECT
    FIELD)= #1.02
    Triggers the user who created this entry.
  • CROSS-REFERENCE:  355.3^AGNA1^MUMPS
    1)= S:$P(^IBA(355.3,DA,0),U,3) ^IBA(355.3,"AGNA",X,+$P(^(0),U,3),DA)=""
    2)= K ^IBA(355.3,"AGNA",X,+$P(^IBA(355.3,DA,0),U,3),DA)
    Cross reference of insurance companies and group names.
  • CROSS-REFERENCE:  355.3^AGNU1^MUMPS
    1)= S:$P(^IBA(355.3,DA,0),U,4) ^IBA(355.3,"AGNU",X,+$P(^(0),U,4),DA)=""
    2)= K ^IBA(355.3,"AGNU",X,+$P(^IBA(355.3,DA,0),U,4),DA)
    Cross reference of insurance companies and group numbers.
.02 IS THIS A GROUP POLICY? 0;2 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  MAY 25, 1993
  • HELP-PROMPT:  If this is a group policy answer "YES" so that other patients may be associated with it. If this is an individual plan answer "NO" and only the current patient can have this policy.
  • DESCRIPTION:  Some policies are indiviual policies and are specific to a patient. Many policies are group plans that many patients may have. If this is a group plan, answer 'YES' so that other patients may be associated with this
    policy.  If this is an individual plan then answer 'NO' and only this patient can be associated with this policy.
.03 GROUP NAME 0;3 FREE TEXT

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>20!($L(X)<2) X
  • LAST EDITED:  MAY 27, 1993
  • HELP-PROMPT:  Answer must be 2-20 characters in length.
  • DESCRIPTION:  If this is a group policy, enter the name of the group that this policy is associated with. This is the name that the insurance company uses to identify the plan. This will appear on the health claims forms in the
    appropriate blocks.  It will also be used to help identify this policy so that other patients with the same plan can be associated with it.
  • CROSS-REFERENCE:  355.3^D
    1)= S ^IBA(355.3,"D",$E(X,1,30),DA)=""
    2)= K ^IBA(355.3,"D",$E(X,1,30),DA)
  • CROSS-REFERENCE:  355.3^AGNA^MUMPS
    1)= S:+^IBA(355.3,DA,0) ^IBA(355.3,"AGNA",+^(0),X,DA)=""
    2)= K ^IBA(355.3,"AGNA",+^IBA(355.3,DA,0),X,DA)
    Cross reference of insurance companies and group names.
.04 GROUP NUMBER 0;4 FREE TEXT

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>17!($L(X)<2) X
  • LAST EDITED:  JUN 11, 1993
  • HELP-PROMPT:  Answer must be 2-17 characters in length.
  • DESCRIPTION:  
    If this is a group policy enter the number which identifies this policy, i.e. group number/code that the insurance company uses to identify this plan.  Answer must be between 1 and 17 characters.
  • CROSS-REFERENCE:  355.3^E
    1)= S ^IBA(355.3,"E",$E(X,1,30),DA)=""
    2)= K ^IBA(355.3,"E",$E(X,1,30),DA)
  • CROSS-REFERENCE:  355.3^AGNU^MUMPS
    1)= S:+^IBA(355.3,DA,0) ^IBA(355.3,"AGNU",+^(0),X,DA)=""
    2)= K ^IBA(355.3,"AGNU",+^IBA(355.3,DA,0),X,DA)
    Cross reference of insurance companies and group names.
.05 IS UTILIZATION REVIEW REQUIRED 0;5 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  FEB 23, 1993
  • HELP-PROMPT:  Answer "YES" if this policy requires Utilization Review for all billable cases. Otherwise, answer "NO".
  • DESCRIPTION:  Answer "YES" if Utilization Review is required by the insurance company for this policy. Answer "NO" if it is not required. The UR staff will automatically be required to follow-up on all billable cases where this field
    is answered "YES".  If the field is answered "NO" then UR follow-up will be considered optional.
.06 IS PRE-CERTIFICATION REQUIRED? 0;6 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  FEB 23, 1993
  • HELP-PROMPT:  Answer "YES" if pre-certification is required by this policy. Otherwise answer "NO".
  • DESCRIPTION:  Answer "YES" if this policy requires Pre-certification of all non-emergent admissions. Answer "NO" if pre-certification is not required. If pre-certification is required but not obtained, follow-up will be required by
    the MCCR tracking module.
.07 EXCLUDE PRE-EXISTING CONDITION 0;7 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUL 02, 1993
  • HELP-PROMPT:  Answer "YES" if this policy excludes any pre existing conditions. Otherwise answer "NO".
  • DESCRIPTION:  Answer "YES" if the policy excludes any pre existing conditions. Answer "NO" if the policy covers any pre existing conditions. If a patient has pre-exisiting conditions that are not covered they should be entered in the
    patient policy comment field.
.08 BENEFITS ASSIGNABLE? 0;8 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  FEB 23, 1993
  • DESCRIPTION:  
    If this policy will allow assignment of benefits then answer YES, otherwise answer NO.  Normally this field will be answered YES.  However, it may be useful to track policies that do not allow for assignment of benefits.
.09 TYPE OF PLAN 0;9 POINTER TO TYPE OF PLAN FILE (#355.1) TYPE OF PLAN(#355.1)

  • LAST EDITED:  NOV 03, 1993
  • HELP-PROMPT:  Enter the type of policy that best describes this policy.
  • DESCRIPTION:  Select the type of plan that best describes this plan. The type of policy will be used to determine if reimbursement for claims from the insurance carrier are appropriate.It will also be used to determine what other
    fields and displays are appropriate for this plan.  If unknown or unsure pick the more general type of plan.
.1 INDIVIDUAL POLICY PATIENT 0;10 POINTER TO VA PATIENT FILE (#2) VA PATIENT(#2)

  • LAST EDITED:  JUN 01, 1993
  • DESCRIPTION:  This is the patient associated with this policy if this is an individual policy.
    If this is an individual policy, the system will store the patient in this field.  Only one patient may be associated with an individual policy.  Many patients can be associated with a group policy.
1.01 DATE ENTERED 1;1 DATE

  • INPUT TRANSFORM:  S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  NOV 02, 1993
  • DESCRIPTION:  
    This is the date that this policy was entered.  It is triggered by the creation of this entry.
  • NOTES:  TRIGGERED by the INSURANCE COMPANY field of the GROUP INSURANCE PLAN File
1.02 ENTERED BY 1;2 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  JUN 03, 1993
  • DESCRIPTION:  
    This is the user who created this entry.  It is automatically triggered by the creation of this entry.
  • NOTES:  TRIGGERED by the INSURANCE COMPANY field of the GROUP INSURANCE PLAN File
1.03 DATE LAST VERIFIED 1;3 DATE

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUN 03, 1993
  • DESCRIPTION:  This is the date that this policy was last verified. A policy is verified by selecting the Verify Policy Action on the Patient Insurance Management screen. Generally this is the last time that somebody contacted the
    insurance company and verified that policy information is correct.
1.04 VERIFIED BY 1;4 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  JUN 03, 1993
  • DESCRIPTION:  
    This is the user who last verified that the policy information is correct.
1.05 DATE LAST EDITED 1;5 DATE

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUN 03, 1993
  • DESCRIPTION:  
    This is the date that this policy was last edited.  It is automatically updated any time a policy is editing using one of the options provided.
1.06 LAST EDITED BY 1;6 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  JUN 03, 1993
  • DESCRIPTION:  
    This is the user who last edited this policy.  It is automatically updated everytime a policy is edited using one of the options.
11 COMMENTS 11;0 WORD-PROCESSING #355.311

  • DESCRIPTION:  
    Enter comments that are specific to this group plan.  Do not enter comments about a specific patient or patient care here.

ICR, Total: 3

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #952
  • INCOME VERIFICATION MATCH
  • IS PRE-CERTIFICATION REQUIRED? (.06).
    Access: Write w/Fileman

    TYPE OF PLAN (.09).
    Access: Write w/Fileman

    ICR #3823
  • ACCOUNTS RECEIVABLE
  • PROSTHETICS
  • GROUP NAME (.03).
    Access: Direct Global Read & w/Fileman

    GROUP NUMBER (.04).
    Access: Direct Global Read & w/Fileman

    TYPE OF PLAN (.09).
    Access: Direct Global Read & w/Fileman

    ICR #5293
  • INSURANCE CAPTURE BUFFER
  • External References

    Name Field # of Occurrence
    ^%DT 1.01+1, 1.03+1, 1.05+1
    NOW^%DTC .01(XREF 2n1.1)
    ^DICR .01(XREF 2n1.4), .01(XREF 3n1.4)

    Global Variables Directly Accessed

    Name Line Occurrences  (* Changed,  ! Killed)
    ^DD( .01(XREF 2n1.4), .01(XREF 3n1.4)
    ^DD(355.3 .01(XREF 2S), .01(XREF 3S)
    ^IBA(355.3 - [#355.3] .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2n1.4), .01(XREF 3S), .01(XREF 3n1.3), .01(XREF 3n1.4), .01(XREF 4S), .01(XREF 4K), .01(XREF 5S)
    .01(XREF 5K), .03(XREF 1S), .03(XREF 1K), .03(XREF 2S), .03(XREF 2K), .04(XREF 1S), .04(XREF 1K), .04(XREF 2S), .04(XREF 2K)
    ^VA(200 - [#200] .01(XREF 3n1.3)

    Naked Globals

    Name Field # of Occurrence
    ^(0 ID.02+1, ID.03+1, ID.04+1, .01(XREF 3n1.3), .01(XREF 4S), .01(XREF 5S), .03(XREF 2S), .04(XREF 2S)
    ^(1 .01(XREF 2S), .01(XREF 2n1.4), .01(XREF 3S), .01(XREF 3n1.3), .01(XREF 3n1.4)

    Local Variables

    Legend:

    >> Not killed explicitly
    * Changed
    ! Killed
    ~ Newed

    Name Field # of Occurrence
    % .01(XREF 2n1.1)
    >> %DT 1.01+1*, 1.03+1*, 1.05+1*
    %H .01(XREF 2n1.1)
    %I .01(XREF 2n1.1)
    >> D0 .01(XREF 2S), .01(XREF 3S), .01(XREF 3n1.3)
    >> DA .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 3n1.3), .01(XREF 4S), .01(XREF 4K), .01(XREF 5S), .01(XREF 5K), .03(XREF 1S), .03(XREF 1K)
    .03(XREF 2S), .03(XREF 2K), .04(XREF 1S), .04(XREF 1K), .04(XREF 2S), .04(XREF 2K)
    >> DIG .01(XREF 2n1.4), .01(XREF 3n1.4)
    >> DIH .01(XREF 2n1.4), .01(XREF 3n1.4)
    >> DIU .01(XREF 2S), .01(XREF 3S)
    DIV .01(XREF 2S), .01(XREF 2n1.1), .01(XREF 2n1.4), .01(XREF 3S), .01(XREF 3n1.3), .01(XREF 3n1.4)
    DIV(0 .01(XREF 2S), .01(XREF 2n1.4), .01(XREF 3n1.3), .01(XREF 3n1.4)
    DUZ .01(XREF 3S)
    U ID.02+1, ID.03+1, ID.04+1, .01(XREF 2S), .01(XREF 2n1.4), .01(XREF 3S), .01(XREF 3n1.3), .01(XREF 3n1.4), .01(XREF 4S), .01(XREF 4K)
    .01(XREF 5S), .01(XREF 5K)
    X .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2n1.1), .01(XREF 2n1.4), .01(XREF 3S), .01(XREF 3n1.3), .01(XREF 3n1.4), .01(XREF 4S), .01(XREF 4K)
    .01(XREF 5S), .01(XREF 5K), .03+1!, .03(XREF 1S), .03(XREF 1K), .03(XREF 2S), .03(XREF 2K), .04+1!, .04(XREF 1S), .04(XREF 1K)
    .04(XREF 2S), .04(XREF 2K), 1.01+1*!, 1.03+1*!, 1.05+1*!
    Y .01(XREF 2S), .01(XREF 3S), 1.01+1, 1.03+1, 1.05+1
    Y(0 .01(XREF 2S), .01(XREF 3n1.3)
    Y(1 .01(XREF 2S), .01(XREF 3S), .01(XREF 3n1.3)
    Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All