Difference between revisions of "DBIA~"

From VistApedia
Jump to: navigation, search
(Added a glossary link to Clinical Case Registries~)
 
(2 intermediate revisions by 2 users not shown)
Line 14: Line 14:
  
  
Source: '''Clinical Case Registries V. 1.0 User Manual'''
+
Source: '''[[Clinical Case Registries~|Clinical Case Registries]] V. 1.0 User Manual'''
 
----
 
----
 
[[Category:Clinical Case Registries]]
 
[[Category:Clinical Case Registries]]
Line 39: Line 39:
 
----
 
----
 
[[Category:Mental Health]]
 
[[Category:Mental Health]]
 +
{{Category:Glossary}}
 +
[[Category:Glossary]]
 +
----
 +
 +
; DBIA
 +
: Database Integration Agreement. A formal understanding between two or more [[application~|Application]] packages which describes how data is shared or how packages interact. This Agreement maintains information between package Developers, allowing the use of internal entry points or other package-specific features.
 +
 +
 +
Source: '''BCMA V. 3.0 Technical Manual/Security Guide'''
 +
----
 +
[[Category:Pharm: Bar Code Medication Administration (BCMA)]]
 
{{Category:Glossary}}
 
{{Category:Glossary}}
 
[[Category:Glossary]]
 
[[Category:Glossary]]

Latest revision as of 08:14, 22 August 2012

DBIA
Database Integration Agreement, a formal understanding between two or more VistA packages which describes how data is shared or how packages interact. The DBA maintains a list of DBIAs.


Source: Spinal Cord Dysfunction V. 2.0 User Manual


This is a Glossary term from the VistA Documentation Library

DBIA
Database Integration Agreement


Source: Clinical Case Registries V. 1.0 User Manual


This is a Glossary term from the VistA Documentation Library

DBIA
Data Base Integration Agreement


Source: Laboratory V. 5.2 Patch LR*5.2*259 AP Electronic Signature User Manual


This is a Glossary term from the VistA Documentation Library

DBIA
Database Integration Agreement


Source: MHA 2 Patch YS*5.01*76 User Manual


This is a Glossary term from the VistA Documentation Library

DBIA
Database Integration Agreement. A formal understanding between two or more Application packages which describes how data is shared or how packages interact. This Agreement maintains information between package Developers, allowing the use of internal entry points or other package-specific features.


Source: BCMA V. 3.0 Technical Manual/Security Guide


This is a Glossary term from the VistA Documentation Library