Difference between revisions of "FILE 1.5"
From VistApedia
DavidWhitten (talk | contribs) (Created page with " Ben Irwin says ENTITY FILE is aimed at REST and JSON for supporting NODE.js. Also may be used to map data elements between VistA and external systems such...") |
DavidWhitten (talk | contribs) |
||
| Line 4: | Line 4: | ||
Also may be used to map data elements between VistA and external systems such as [[Cerner]]. | Also may be used to map data elements between VistA and external systems such as [[Cerner]]. | ||
| − | According to [[Sam Habiel]] on 12-MAR-2019 the | + | According to [[Sam Habiel]] on 12-MAR-2019 the [[PATCH DI*22.2*9]] / [[PATCH VPR*1*8]]: Fileman: Provide the new Entity file that provides the ability to map VistA files & fields to other data models, and extract objects into [[XML]] or JSON. The [[VPR]] patch will populate the new entity file to map VistA data elements to [[Intersystems]] [[SDA model]]. It will also add the monitoring of clinical data events initially deployed for [[eHMP]]. |
Latest revision as of 20:02, 20 March 2019
Ben Irwin says ENTITY FILE is aimed at REST and JSON for supporting NODE.js.
Also may be used to map data elements between VistA and external systems such as Cerner.
According to Sam Habiel on 12-MAR-2019 the PATCH DI*22.2*9 / PATCH VPR*1*8: Fileman: Provide the new Entity file that provides the ability to map VistA files & fields to other data models, and extract objects into XML or JSON. The VPR patch will populate the new entity file to map VistA data elements to Intersystems SDA model. It will also add the monitoring of clinical data events initially deployed for eHMP.
