| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
| 80 | DBIA80-A | File | CLINICAL PROCEDURES | 1991/02/05 | APPROVED | Active | Controlled Subscription | 690 | This DBIA documents references to the MEDICAL PATIENT file (#690). |
|||
| 147 | DBIA147-A | Other | CLINICAL PROCEDURES | 1992/03/11 | APPROVED | Active | Private | 1. The REQUEST/CONSULTATION file, 123, has a variable pointer field called "Results" which points to the following fields. 691 Echo Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 691.1 Cardiac Catheterization Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 691.5 Electrocardiogram (EKG/ECG) Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 691.6 Holter Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 691.7 Exercise Tolerance Test Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 691.8 Electrophysiology (EP) Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 694 Hematology Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 698 Generator Implant 698V1 V Lead Implant 698.2 A Lead Implant 698.3 Pacemaker Surveillance 699 Endoscopy/Consult Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 700 Pulmonary Function Tests Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 701 Rheumatology |
||||
| 540 | DBIA80-B | File | CLINICAL PROCEDURES | 1991/02/05 | APPROVED | Active | Private | 699 | The Health Summary exports and calls the routine GMTSMCPS, which generates the output for the Health Summary Medicine component. The following fields and cross references are being referenced: ^MCAR(699, Endoscopy File Fields: 1 Procedure 20 Summary |
|||
| 541 | DBIA80-C | File | CLINICAL PROCEDURES | 1991/02/05 | APPROVED | Active | Private | 694 | The Health Summary exports and calls the routine GMTSMCPS, which generates the output for the Health Summary Medicine component. The following fields and cross references are being referenced: ^MCAR(694, Hematology File Fields: 2 Procedure 1.5 Summary |
|||
| 542 | DBIA80-D | File | CLINICAL PROCEDURES | 1991/02/05 | APPROVED | Active | Private | 697.2 | The Health Summary exports and calls the routine GMTSMCPS, which generates the output for the Health Summary Medicine component. The following fields and cross references are being referenced: ^MCAR(697.2, Procedure Location File Fields: .01 Name 1 Global Location Uses "C" cross reference on Global Location field. The "C" cross reference could result in pointing to global locations in the Global Location field which currently contains global roots for the range on files from ^MCAR(691, through ^MCAR(699,. |
|||
| 615 | DBIA147-B | Routine | CLINICAL PROCEDURES | 1992/03/11 | APPROVED | Active | Private | 2. This results pointer is updated via calls from the Medicine options which enter/edit results to EN^GMRCR and RESULT^GMRCR, which are documented in the Consult/Request Tracking package. Once the results variable pointer is defined, the Medicine Package has provided Consult/Request Tracking with an entry point PRINT^MCOR which extracts results information and stores them in an ^TMP array for display purposes in OE/RR and Consult/Request Tracking. In order to call PRINT^MCOR the Consult/Request Tracking package must define the following variables. ORACTION=8 GMRCSR=variable pointer to results file GMRCPRNM=Name of procedure type, which should equal one of the Procedure Types in File 697.2, the eighth piece. The call to get the Medicine Results formats the results in ^TMP("MC",$J,... The ^TMP("MC",$J temporary global may be deleted upon completion of use. |
MCOR | |||
| 616 | DBIA147-C | File | CLINICAL PROCEDURES | 1992/03/11 | APPROVED | Active | Private | 697.2 | 3. In addition to the interface the Medicine Package has provided, an alternative method for the Medicine Package Users is provided in a stand alone option provided by the Consult/Request Tracking Package. This option functions as follows: - The user selects the Medicine Procedure Type from a Protocol Menu - The service related to the Procedure Type defined in the FILE LINK field in Protocol File is determined - The patient is selected. - Consults/Request for the Service and Patient are displayed. - At the Select Action: prompt, the user may select "AR" for associate results - The PRINT NAME field, in the 8th piece of the ^MCAR(697.2,D0,0) node is the text that the Consults package uses to do a look up on the "BA" cross-reference. The consult package gets the text for the look-up from the Protocol name by removing the "GMRCR " prefix. The result of the "BA" lookup allows us to find the entry in 697.2 that represents the type of procedure that consults is processing. The GLOBAL LOCATION, the 2nd piece of the ^MCAR(697.2,D0,0) global node tells Consults what file to look for the results in. A look-up in the GLOBAL LOCATION file allows the user to "ASSOCIATE RESULTS" with a consult, and provide the Medicine package with the consult it is linked to. - The user is allowed to select from the list of Results in this results file for the Patient. (Using Medicine "C" cross-ref.) - Once a result entry is selected, it may be viewed using the PRINT^MCOR, to verify these are the correct results to associate with the request. - The user is asked if the order status should be updated to 'Completed' (default is yes, if no, ORSTS is incomplete) - The user is asked to enter the name of the clinician responsible for the results. |
|||
| 1189 | DBIA1189-A | File | CLINICAL PROCEDURES | 1995/04/03 | APPROVED | Active | Private | The purpose of this agreement is to provide access to the Medicine package (custodian) by the Imaging package (subscriber) for the purpose of creating a new Medicine package entry (stub:Pt ID, Date/time) as a holder of an Imaging pointer or set of Imaging pointers. The Imaging pointers are set in the field 2005, as descendants of the 0 subscript of node 2005 in each of the following files: Echo(691), Cardiac Cath(691.1), EKG(691.5), Hematology(694), Endoscopy(699), Generalized Procedure(699.5), and Rheumatology(701). In addition, the MEDICAL PATIENT field (location 0;2) is also permitted for Direct Global Read. The Imaging routines which perform this function are as follows: MAGMCPT* and MAGUFILR |
||||
| 1190 | DBIA1189-B | File | CLINICAL PROCEDURES | 1995/04/03 | APPROVED | Active | Private | The purpose of this agreement is to provide access to the Medicine package (custodian) by the Imaging package (subscriber) for the purpose of editing (including deletion of) Medicine package Image entries. The Imaging pointers are set in the field 2005, as descendants of the 0 subscript of node 2005 on each of the following files: Echo(691), Cardiac Cath(691.1), EKG(691.5), Hematology(694), Endoscopy(699), Generalized Procedure(699.5), and Rheumatology(701). The Imaging routines which perform this function are as follows: MAGMCPT*, MAGUDEL* and MAGUFILR. |
||||
| 1191 | DBIA1189-C | File | CLINICAL PROCEDURES | 2003/10/20 | Retired | Private | The purpose of this agreement is to provide access to the Medicine package (custodian) by the Imaging package (subscriber) for the purpose of displaying Medicine package Summary fields associated with Images. The Imaging functions require direct global read access to the Procedure/Subspecialty file (697.2), the Image multiple of each of the Medicine Procedure files listed below, and the Summary field each of the Files Listed below. Medicine Procedure Files: Echo(691), Cardiac Cath(691.1), EKG(691.5), Hematology(694), Endoscopy(699), Generalized Procedure(699.5), and Rheumatology(701). The Imaging routines which perform this function are as follows: MAGDISP, MAGMIM, MAGSUM, and MAGABLP. |
|||||
| 1193 | DBIA1193 | Routine | CLINICAL PROCEDURES | 1995/04/06 | APPROVED | Active | Private | This privately supported entry point allows the display the full Medicine report associated with the Imaging Workstation Display. The routine MCMAGDSP has an entry point of REPRT which, when passed the IEN and the Medicine package file number, will display the full report to the Workstation (only). This routine (MCMAGDSP) will be bundled in a patch to Medicine 2.2. It contains display functionality for the following types of Medicine procedures: Electrocardiograms (ECG), Echocardiography (ECHO), Cardiac Catheterization, Hematology (Bone Marrow biopsies and aspirates), Pulmonary Endoscopies, Gastrointestinal Endoscopies, Medicine Consults, Generic Procedures, and Rheumatology. This is the current extent of Medicine procedures that have Imaging pointer fields. This reporting functionality uses the Procedure/Subspecialty file in tandem with the result files to determine the type of procedure. This is necessary as many of the results files share a common structure to house data of different procedure types (as in different CPTs). The MCMAGDSP routine uses the same compiled print templates that Medicine uses and there are also calls to utilities of the common Medicine print driver. |
MCMAGDSP | |||
| 1207 | DBIA1207 | Routine | CLINICAL PROCEDURES | 1995/05/04 | APPROVED | Active | Supported | 1) Decision Support System (DSS) interface Functional description: This process provides a reporting mechanism to the DSS package. The subscriber passes a Starting date and ending date to the MCARDSS routine and the TMP global will store the result records in an arbitrary order. The results include the following required fields: Date and Time the record is released, Provider signing or signed for, CPT code, Patient identification Software components: Routines -- ^MCARDSS, ^MCBLD, ^MCPTF File(s) -- Procedure Term File: ^MCAR(694.8 Menu Options: None Technical overview: The DSS application makes a parameterized call to ^MCARDSS(Start_date,End_date) with dates in regular Fileman date/time format. Only results which have a valid signature, CPT code, date signed, and valid patient ID will be returned in the ^TMP($J,count) scratch global. The result is stored as follows: Provider ID(DUZ)^Patient ID(DFN)^Date/time signed(FM DATE/TIME)^CPT code for example -- ^TMP(1231231,3)=194^2323^295101010.1232^93005 |
MCARDSS | |||
| 1236 | DBIA1236 | Routine | CLINICAL PROCEDURES | 1995/06/16 | APPROVED | Active | Private | To support Medicine 2.2 with 4 new components the $$HL7^MCORMN(MESSNUM) entry point needs to be called. This interface will allow Health Summary to get patient data for a breif summary, a brief summary for only abnormal values, a full summary and a full captioned summary. It will also support the existing one line medicine summary. This interface is setup in an HL7 compliant manner. HS will need to have the Pateint DFN, Beginning Date, Ending Date, # of occurrences, and Type of Date (Full or Brief) set into a message via the ^XMD call. The $$HL7^MCORMN(MESSNUM) call will retrieve the available data based on the above specifications and using the message number returned from the ^XMD call. Data that will be returned via the message is DATE/TIME, PROCEDURE, SUMMARY, PROCEDURE SUMMARY, and the PROCEDURE REPORT. |
MCORMN | |||
| 1999 | DBIA1999 | File | CLINICAL PROCEDURES | 2003/10/20 | Retired | Private | 690 | By providing read access to file 690, the Medical Patient file, offer the user a list of existing medicine procedures to apphend Images to. For a list of patient procedures Imaging reads: ^MCAR(690,"AC",DFN,Inverted FM Date/Time,File #) This IA will be modified as Medicine APIs are released to replace its functions. Imaging and Medicine will participate actively in the testing process to be sure API's meet Imaging's needs. Imaging will migrate to the use of API's as soon as possible. |
||||
| 2000 | DBIA2000 | File | CLINICAL PROCEDURES | 2003/10/20 | Retired | Private | 697.2 | |||||
| 2001 | DBIA2001 | File | CLINICAL PROCEDURES | 2003/10/20 | Withdrawn | Private | 691 | For the purpose of appending an Image to an existing Medicine procedure or placing an Image into a new Medicine Procedure read/write access is require for ECHOCARDIOGRAPHY. FILE^DICN is used to create a new file 691 entry, when necessary. The IMAGE multiple, field 2005, is processed by direct global read/writes. This IA will be modified as Medicine APIs are released to replace its functions. Imaging and Medicine will participate actively in the testing process to be sure API's meet Imaging's needs. Imaging will migrate to the use of API's as soon as possible. |
||||
| 2002 | DBIA2002 | File | CLINICAL PROCEDURES | 1997/04/10 | Withdrawn | Private | 691.1 | For the purpose of appending an Image to an existing Medicine procedure or placing an Image into a new Medicine Procedure read/write access is require for CARDIAC CATHETERIZATION. FILE^DICN is used to create a new file 691.1 entry,when necessary. The IMAGE multiple, field 2005, is processed by direct global read/writes. |
||||
| 2003 | DBIA2003 | File | CLINICAL PROCEDURES | 1997/04/11 | Withdrawn | Private | 691.5 | For the purpose of appending an Image to an existing Medicine procedure or placing an Image into a new Medicine Procedure read/write access is require for ELECTROCARDIOGRAM. FILE^DICN is used to create a new file 691.5 entry,when necessary. The IMAGE multiple, field 2005, is processed by direct global read/writes. |
||||
| 2004 | DBIA2004 | File | CLINICAL PROCEDURES | 1997/04/11 | Withdrawn | Private | 694 | For the purpose of appending an Image to an existing Medicine procedure or placing an Image into a new Medicine Procedure read/write access is require for HEMATOLOGY. FILE^DICN is used to create a new file 694 entry, when neccessary. The IMAGE multiple, field 2005, is processed by direct global read/writes. |
||||
| 2006 | DBIA2006 | File | CLINICAL PROCEDURES | 1997/04/11 | Withdrawn | Private | 699 | For the purpose of appending an Image to an existing Medicine procedure or placing an Image into a new Medicine Procedure read/write access is require for ENDOSCOPY/CONSULT. FILE^DICN is used to create a new file 699 entry,when necessary. The IMAGE multiple, field 2005, is processed by direct global read/writes. |
||||
| 2007 | DBIA2007 | File | CLINICAL PROCEDURES | 1997/04/11 | Withdrawn | Private | 699.5 | For the purpose of appending an Image to an existing Medicine procedure or placing an Image into a new Medicine Procedure read/write access is require for GENERALIZED PROCEDURE/CONSULT. FILE^DICN is used to create a new file 699.5 entry, when nessary. The IMAGE multiple, field 2005, is processed by direct global read/writes. |
||||
| 2008 | DBIA2008 | File | CLINICAL PROCEDURES | 1997/04/11 | Withdrawn | Private | 701 | For the purpose of appending an Image to an existing Medicine procedure or placing an Image into a new Medicine Procedure read/write access is require for RHEUMATOLOGY. FILE^DICN is used to create a new file 701 entry, when necessary. The IMAGE multiple, field 2005, is processed by direct global read/writes. |
||||
| 2009 | DBIA2009 | Routine | CLINICAL PROCEDURES | 2003/10/20 | Retired | Private | This supported reference allows the Imaging package user to view a medicine package textual report which is linked to the image. |
MCMAGDSP | ||||
| 2017 | DBIA2017 | Routine | CLINICAL PROCEDURES | 1997/04/30 | Pending | Private | This DBIA implements two new Medicine APIs for the Imaging package to call. The UPDATE^MCUIMAG0() API creates new entries, if needed, in the Medical Patient file and the Medicine Procedure data files. It also allows the Imaging package to populate the Image multiple in the Medicine Procedure data files. The KILL^MCUIMAG0() API removes entries from the Image multiples in the Medicine Procedure data files. |
MCUIMAGO | ||||
| 2039 | MEDICINE UPDATE API | Routine | CLINICAL PROCEDURES | 1997/06/24 | APPROVED | Active | Controlled Subscription | This entry point creates new entries, if needed, in the Medical Patient file (#690) and the Medicine Procedure data files (see file list under MCD0). It also allows the Imaging package to populate the Image multiple in the Medicine Procedure data files. |
MCUIMAG0 | |||
| 2040 | MEDICINE KILL API | Routine | CLINICAL PROCEDURES | 1997/06/24 | APPROVED | Active | Controlled Subscription |
This entry point removes entries from the Image multiples in the Medicine Procedure data files. |
MCUIMAG0 | |||
| 2757 | OE/RR calls to MCARPS2 | Routine | CLINICAL PROCEDURES | 1999/02/18 | APPROVED | Active | Controlled Subscription | This DBIA authorizes OE/RR v3 calling EN^MCARPS2(DFN) |
MCARPS2 | |||
| 2986 | OE/RR calls to MCARP | Routine | CLINICAL PROCEDURES | 1999/11/15 | APPROVED | Active | Private | This routine is used to get parameters needed to produce a report of Patient Procedures. This DBIA is only to be used for CPRS Reporting and does not include any procedures for editing the Medicine database. |
MCARP | |||
| 3042 | SINGLE PROCEDURE DISPLAY API | Routine | CLINICAL PROCEDURES | 2000/02/16 | APPROVED | Active | Private |
This DBIA authorizes CONSULT/REQUEST TRACKING to call ^MCAPI for the purpose of retrieving a single patient procedure and displaying the selected procedure in the Consult/Request Tracking Package. |
MCAPI | |||
| 3138 | DBIA3138 | Routine | CLINICAL PROCEDURES | 2000/06/28 | Retired | Private | This DBIA is used to document the usage of the API $$PDATETM^MDCON(MDINST). |
MDCON | ||||
| 3139 | DBIA3139 | File | CLINICAL PROCEDURES | 2000/06/28 | APPROVED | Active | Controlled Subscription | 702.01 | ||||
| 3249 | Imaging Medicine Procedure field | Routine | CLINICAL PROCEDURES | 2000/11/14 | APPROVED | Active | Private | Vista Imaging is requesting permission to use API $$PRCFLD^MCUIMAG0. This is needed needed to lookup the Procedure/Subspecialty pointer field during an image capture via the DICOM Image gateway. The gateway receive images directly from Image Acquisition devices (IFA, Olympus, etc.) and each device sends a pseudo transaction number consisting of the Medicine file and internal entry number for the images to be attached to. This call is required to get the procedure field name/number to do a Fileman lookup on the entry sent. |
MCUIMAG0 | |||
| 3250 | Imaging 3250 | Routine | CLINICAL PROCEDURES | 2000/11/14 | APPROVED | Active | Private | Vista Imaging is requesting permission to call $$VALID^MCUIMAG0 to validate an entry in a Medicine file. This is used on an Imaging workstation to obtain a psuedo transaction number to be used to capture DICOM images directly from image acquisition devices (IFA, Olympus, etc.). |
MCUIMAG0 | |||
| 3251 | Imaging 3251 | Routine | CLINICAL PROCEDURES | 2000/11/14 | Withdrawn | Private | Vista Imaging is requesting permission to call KILL^MCUIMAG0. This is required to delete an image pointer in a Medicine file entry. |
MCUIMAGO | ||||
| 3253 | Imaging 3253 | File | CLINICAL PROCEDURES | 2000/11/15 | Withdrawn | Private | 691 | This request is for the purpose of displaying a list of entries for a specified patient and date range in the Medicine file 691 (ECHO). Vista Imaging is acquiring images directly from modalities and on occassion the provided pseudo transaction number assigned is incorrect and the automatic image processing will require user interaction. During this user interaction the user will be provided with the patient name of the failed image. The end-user will need to match the image to a Medicine file entry that is displayed on the screen. |
||||
| 3254 | Imaging 3254 | File | CLINICAL PROCEDURES | 2000/11/15 | Withdrawn | Private | 694 | This request is for the purpose of displaying a list of entries for a specified patient and date range in the Medicine file 694 (HEMATOLOGY) Vista Imaging is acquiring images directly from modalities and on occasion the provided pseudo transaction number assigned is incorrect and the automatic image processing will require user interaction. During this user interaction the user will be provided with the patient name of the failed image. The end-user will need to match the image to a Medicine file entry that is displayed on the screen. |
||||
| 3255 | Imaging 3255 | File | CLINICAL PROCEDURES | 2000/11/15 | Withdrawn | Private | 691.1 | This request is for the purpose of displaying a list of entries for a specified patient and date range in the Medicine file 691.1 (CARDIAC CATHETERIZATION) Vista Imaging is acquiring images directly from modalities and on occasion the provided pseudo transaction number assigned is incorrect and the automatic image processing will require user interaction. During this user interaction the user will be provided with the patient name of the failed image. The end-user will need to match the image to a Medicine file entry that is displayed on the screen. |
||||
| 3256 | IMAGING 3256 | File | CLINICAL PROCEDURES | 2000/11/15 | Withdrawn | Private | 691.5 | This request is for the purpose of displaying a list of entries for a specified patient and date range in the Medicine file 691.5 (ELECTROCARDIOGRAPHY). Vista Imaging is acquiring images directly from modalities and on occasion the provided pseudo transaction number assigned is incorrect and the automatic image processing will require user interaction. During this user interaction the user will be provided with the patient name of the failed image. The end-user will need to match the image to a Medicine file entry that is displayed on the screen. |
||||
| 3257 | IMAGING 3257 | File | CLINICAL PROCEDURES | 2000/11/15 | Withdrawn | Private | 699 | This request is for the purpose of displaying a list of entries for a specified patient and date range in the Medicine file 699 (ENDOSCOPY). Vista Imaging is acquiring images directly from modalities and on occasion the provided pseudo transaction number assigned is incorrect and the automatic image processing will require user interaction. During this user interaction the user will be provided with the patient name of the failed image. The end-user will need to match the image to a Medicine file entry that is displayed on the screen. |
||||
| 3258 | IMAGING 3258 | File | CLINICAL PROCEDURES | 2000/11/15 | Withdrawn | Private | 699.5 | This request is for the purpose of displaying a list of entries for a specified patient and date range in the Medicine file 699.5 (GENERIC MEDICINE). Vista Imaging is acquiring images directly from modalities and on occasion the provided pseudo transaction number assigned is incorrect and the automatic image processing will require user interaction. During this user interaction the user will be provided with the patient name of the failed image. The end-user will need to match the image to a Medicine file entry that is displayed on the screen. |
||||
| 3279 | MCARUTL2 | Routine | CLINICAL PROCEDURES | 2001/01/02 | APPROVED | Active | Supported |
These APIs allow the Imaging package access to the Medicine package data. The APIs will do lookups on the MEDICAL PATIENT File (#690) and the PROCEDURE/SUBSPECIALTY file (#697.2) and return data from the associated Medicine files. |
MCARUTL2 | |||
| 3280 | MCARUTL3 | Routine | CLINICAL PROCEDURES | 2001/01/02 | APPROVED | Active | Supported |
This API allows the Imaging package access to the Medicine package data. The API will do a lookup on the MEDICAL PATIENT File (#690) and the PROCEDURE/SUBSPECIALTY file (#697.2) for the indicated entry and return the associated Medicine package data. |
MCARUTL3 | |||
| 3321 | DBIA 3321 | Other | CLINICAL PROCEDURES | 2001/02/26 | APPROVED | Active | Controlled Subscription | Medicine gives permission to the VistA Imaging application to copy the following routines into their Imaging gateways. These routines are not renamed or modified at the destination. |
||||
| 3378 | DBIA3378 | Routine | CLINICAL PROCEDURES | 2005/04/07 | APPROVED | Active | Controlled Subscription | This IA documents calls to MDAPI. |
MDAPI | |||
| 3613 | Imaging - Visit Info | Routine | CLINICAL PROCEDURES | 2002/07/03 | APPROVED | Active | Private | Imaging has permission, for a limited time, to call GETVST^MDRPCOP and obtain a list of patient visit information. The time frame to be identified by Clinical Procedures when the code in GETVST^MDRPCOP is changed to call the approved API (SELECTED^VSIT). Clinical Procedures will coordinate with Imaging on the release of the patch and identify the passing parameters used in the call to SELECTED^VSIT to ensure continuity with both applications (Imaging and Clinical Procedures). |
MDRPCOP | |||
| 3778 | DBIA3778 | Routine | CLINICAL PROCEDURES | 2002/10/07 | APPROVED | Active | Private | This IA documents the HL1^MCORMN(SAP,PATID,BDATE,EDATE,OCC,ATYPE) entry point in Medicine version 2.3 after the installation of patch MC*2.3*36. This interface will allow Health Summary to get patient data for a brief summary, a brief summary for only abnormal values, a full summary, a full captioned summary, and one line medicine summary. This interface is setup in an HL7 compliant manner. HS will need to have the Patient DFN, Beginning Date, Ending Date, # of occurrences, and Type of report (Full or Brief). The HL1^MCORMN(SAP,PATID,BDATE,EDATE,OCC,ATYPE) call will retrieve data based on the above specifications and returned the data via a ^TMP("MCAR1",$J,#) global. The data that will be returned is the DATE/TIME, PROCEDURE, SUMMARY, PROCEDURE SUMMARY, and the PROCEDURE REPORT. |
MCORMN | |||
| 3780 | DBIA3780 | Routine | CLINICAL PROCEDURES | 2002/10/08 | APPROVED | Active | Private | This IA documents the API interface between Medicine version 2.3 and Immunology Case Registry version 2.1. Prior to calling the API GET^MCARAPI(RESULTS,MCARDFN,MCSDT,MCEDT,MCFLDS), ICR should check the existence of patch MC*2.3*34. |
MCARAPI | |||
| 3854 | DBIA3854 | Routine | CLINICAL PROCEDURES | 2002/11/26 | APPROVED | Active | Private | This IA documents the API interface between Clinical Procedures and Clinical Case Registries version 1.0. Prior to calling the API GET^MDAPI1(RESULTS,MDARDFN,MDSDT,MDEDT,MDFLDS), the subscriber should check the existence of patch MD*1*1. |
MDAPI1 | |||
| 4230 | DBIA4230 | Routine | CLINICAL PROCEDURES | 2004/05/25 | APPROVED | Active | Controlled Subscription | This DBIA documents the usage of the MDPS1 entry points for displaying the Clinical Procedures result reports. |
MDPS1 | |||
| 5076 | MDCLIO1 | Routine | CLINICAL PROCEDURES | 2008/01/17 | Other | Private | The MDCLIO1 routine provides Clinical Observations data. Note: This API is only for the Vitals package and will not be approved for other packages. |
MDCLIO1 | 2008/03/19 | |||
| 5269 | MDTERM | Routine | CLINICAL PROCEDURES | 2008/10/02 | APPROVED | Active | Private | MDTERM | 2010/03/04 | |||
| 5350 | MEDICAL PATIENT IEN | File | CLINICAL PROCEDURES | 2009/01/15 | Pending | Private | In CPRS v27, incorrect patient information could be displayed to the user. In Consults, when the incorrect patient information was displayed, the user could attach a result note to the wrong patient's record. Therefore, an agreement with Clinical Procedures is needed to allow the MEDICAL PATIENT IEN to be pulled from the Medicine files using $$GET1^DIQ based upon the Medicine Results stored in REQUEST/CONSULTATION file #123. The IEN value will be reported on a Consults report which finds all ASSOCIATED RESULTS that are attached to the wrong patient. This IA will be used one time for patch GMRC*3.0*70. FILE# FIELD# NODE ------ ------- ----- 690 MEDICAL PATIENT .01 NAME 0;1 Read w/Fileman 691 ECHO 1 MEDICAL PATIENT 0;2 Read w/Fileman 691.1 CARDIAC CATHETERIZATION 1 MEDICAL PATIENT 0;2 Read w/Fileman 691.5 ELECTROCARDIOGRAM (EKG) 1 MEDICAL PATIENT 0;2 Read w/Fileman 691.6 HOLTER 1 MEDICAL PATIENT 0;2 Read w/Fileman 691.7 EXERCISE TOLERANCE TEST 1 MEDICAL PATIENT 0;2 Read w/Fileman 691.8 ELECTROPHYSIOLOGY (EP) 1 MEDICAL PATIENT 0;2 Read w/Fileman 694 HEMATOLOGY 1 MEDICAL PATIENT 0;2 Read w/Fileman 698 GENERATOR IMPLANT 1 MEDICAL PATIENT 0;2 Read w/Fileman 698.1 V LEAD IMPLANT 1 MEDICAL PATIENT 0;2 Read w/Fileman 698.2 A LEAD IMPLANT 1 MEDICAL PATIENT 0;2 Read w/Fileman 698.3 PACEMAKER SURVEILLANCE 1 MEDICAL PATIENT 0;2 Read w/Fileman 699 ENDOSCOPY/CONSULT .02 MEDICAL PATIENT 0;2 Read w/Fileman 699.5 GENERALIZED PROCEDURE/CONSULT .02 MEDICAL PATIENT 0;2 Read w/Fileman 700 PULMONARY FUNCTION TESTS 1 MEDICAL PATIENT 0;2 Read w/Fileman 701 RHEUMATOLOGY 1 MEDICAL PATIENT 0;2 Read w/Fileman |
|||||
| 5748 | CLIO TERM FILE | File | CLINICAL PROCEDURES | 2011/11/16 | APPROVED | Active | Private | 704.101 | 2013/03/26 | |||
| 5809 | CLIO TERM TYPE FILE | File | CLINICAL PROCEDURES | 2012/06/11 | APPROVED | Active | Private | 704.102 | 2013/03/26 | |||
| 5810 | CLIO OBS FILE | File | CLINICAL PROCEDURES | 2012/06/11 | APPROVED | Active | Private | 704.117 | 2013/03/26 | |||
| 5811 | CLIO OBS QUALIFIER FILE | File | CLINICAL PROCEDURES | 2012/06/11 | APPROVED | Active | Private | 704.118 | 2013/03/26 | |||
| 5995 | CLIO OBS SET FILE | File | CLINICAL PROCEDURES | 2013/07/29 | APPROVED | Active | Private | 704.116 | 2014/01/14 | |||
| 5996 | CLIO OBS SET OBS PAIR FILE | File | CLINICAL PROCEDURES | 2013/07/29 | APPROVED | Active | Private | 2014/01/14 | ||||
| 5999 | CLIO OBS FLOWSHEET SUPP PAGE FILE | File | CLINICAL PROCEDURES | 2013/07/30 | APPROVED | Active | Private | 2014/01/14 | ||||
| 6084 | MDC OBSERVATION UPDATE | Other | CLINICAL PROCEDURES | 2014/08/14 | APPROVED | Active | Controlled Subscription | The MDC OBSERVATION UPDATE protocol is used to notify other packages when observation data is updated. |
2014/09/05 | |||
| 6729 | MD CLIO | Remote Procedure | CLINICAL PROCEDURES | 2017/01/26 | APPROVED | Active | Private | MD CLIO | 2017/02/28 | |||
| 6828 | ACCESS TO READ EKG FILE | File | CLINICAL PROCEDURES | 2017/10/30 | APPROVED | Active | Private | 691.5 | Users need the ability to access the patient EKG Date/Time, Summary and AUTO Instrument Diagnosis using a Health Summary Object. Routines will use the "C" cross reference to obtain data for a patient using a Fileman call. |
2018/04/12 | ||
| 6928 | CP DICOM INTEROPERABILITY | File | CLINICAL PROCEDURES | 2018/06/15 | APPROVED | Active | Private | 702.09 | 2018/06/15 | |||
| 6929 | CP DICOM INTEROPERABILITY TRANSACTIONS | File | CLINICAL PROCEDURES | 2018/06/15 | APPROVED | Active | Private | 702 | 2018/06/15 | |||
| 6930 | CP DICOM INTEROPERABILITY DEFINITIONS | File | CLINICAL PROCEDURES | 2018/06/15 | APPROVED | Active | Private | 702.01 | 2018/06/15 | |||
| 6985 | CP TRANSACTIONS DATA | File | CLINICAL PROCEDURES | 2018/10/26 | APPROVED | Active | Private | 702 | This agreement documents VPR access to fields in the CP Transactions file #702 that are not available via other api's. |
2018/10/31 |