Difference between revisions of "VitalCenter Online - Archival Solution Overview"
(Created page with "Category:Webcasts __TOC__ ==Description== This webcast provides an overview of key drivers behind archiving legacy system data, key different between archived and convers...") |
|||
| (9 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
==Presentation Materials== | ==Presentation Materials== | ||
Presented May 4, 2016 by David Burkhead | Presented May 4, 2016 by David Burkhead | ||
| − | + | [[Media: VitalCenter Online - Archival Overview Slide Deck.pdf|Download the slide deck here]] | |
| − | [[Media: VitalCenter Online - Archival Overview.pdf|Download the slide deck]] | ||
==Q&A== | ==Q&A== | ||
| − | '''Q: | + | '''Q: Does or will your archive currently support the concept of an EMPI value?''' |
| − | '''A:''' | + | '''A:''' ''Yes, VitalCenter Online – Archival does support the ability to store an EMPI value at the patient level.'' |
| − | |||
| − | |||
| − | |||
| − | '''A:''' | + | '''Q: In our system we currently have results that can be stored as images in order to assist with order reconciliation and certain MU based workflows; are you able to store results in that way within the archive?''' |
| − | + | ||
| − | + | '''A:''' ''Yes we will provide the ability to associate scanned images (again specific within the details of the source data) as result items so that they would display under the appropriate data category in the archive as well.'' | |
| − | + | ||
| − | + | ||
| − | + | '''Q: Could you explain a little bit about how you handle purging data from the archive? Is this possible?''' | |
| − | + | ||
| − | + | '''A:''' ''Yes, this is something that we will work with your organization on, depending on both location and retention policies we can help implement this to an extent that is partially automated; for example, implementing it in a way that would ensure records under current legal hold are excluded.'' | |
| − | + | ||
| − | + | ||
| + | '''Q: Will your archive offer any place to store data sets that are not standard or pre-defined in the archive?''' | ||
| + | |||
| + | '''A:''' ''VitalCenter Online’s architecture allows us to handle any shape of data without having to modify our software; giving us significant flexibility to implement additional patient/non-patient data sets.'' | ||
| + | |||
| + | |||
| + | '''Q: Does your solution offer a way to handle data from multi-org environments where the data source may technically be from the same data source, but the patient records are not shared in the EMR?''' | ||
| + | |||
| + | '''A:''' ''Yes, during the data extract and prior to the data import process into the ArchiveETL we would work with the source data provided to essentially treat those as different sources; at that point we then restrict which particular data sources user(s) have access to from their setup and configuration.'' | ||
| + | |||
| + | |||
| + | '''Q: How is VitalCenter Online – Archival deployed and hosted?''' | ||
| + | |||
| + | '''A:''' ''VitalCenter is a software as a service application and therefore all of our infrastructure is run and maintained by Galen. Delivering the software in this way allows us to iterate and improve on the software as rapidly as possible and minimize the cost to our customers.'' | ||
| + | |||
| + | |||
| + | '''Q: What type of additional technical security measures have you incorporated into your solution? Could you provide more detail around that?''' | ||
| + | |||
| + | '''A:''' ''From a compliance perspective it is both HIPAA and HITECH compliant. The auditing trail specific to VCO is fully integrated and includes reporting. Data is always encrypted; at rest and in-motion. All customer data is completely isolated – there is no sharing of storage (i.e., databases). Our data center has multiple independent security and compliant certifications and attestations including:'' | ||
| + | *''P-ATO (Provisional Authority to Operate)'' | ||
| + | *''FERPA (Family Educational Rights and '' | ||
| + | *''FIPS (Federal Information Processing Standard)'' | ||
| + | *''FISMA (Federal Information Security Management Act)'' | ||
| + | *''HIPAA'' | ||
| + | *''ISO/IEC 27001'' | ||
| + | *''SOC (Service Organization Controls)'' | ||
Latest revision as of 18:14, 6 May 2016
Description
This webcast provides an overview of key drivers behind archiving legacy system data, key different between archived and conversion based data, and an overview of Galen's VitalCenter Online - Archival solution.
Presentation Materials
Presented May 4, 2016 by David Burkhead Download the slide deck here
Q&A
Q: Does or will your archive currently support the concept of an EMPI value?
A: Yes, VitalCenter Online – Archival does support the ability to store an EMPI value at the patient level.
Q: In our system we currently have results that can be stored as images in order to assist with order reconciliation and certain MU based workflows; are you able to store results in that way within the archive?
A: Yes we will provide the ability to associate scanned images (again specific within the details of the source data) as result items so that they would display under the appropriate data category in the archive as well.
Q: Could you explain a little bit about how you handle purging data from the archive? Is this possible?
A: Yes, this is something that we will work with your organization on, depending on both location and retention policies we can help implement this to an extent that is partially automated; for example, implementing it in a way that would ensure records under current legal hold are excluded.
Q: Will your archive offer any place to store data sets that are not standard or pre-defined in the archive?
A: VitalCenter Online’s architecture allows us to handle any shape of data without having to modify our software; giving us significant flexibility to implement additional patient/non-patient data sets.
Q: Does your solution offer a way to handle data from multi-org environments where the data source may technically be from the same data source, but the patient records are not shared in the EMR?
A: Yes, during the data extract and prior to the data import process into the ArchiveETL we would work with the source data provided to essentially treat those as different sources; at that point we then restrict which particular data sources user(s) have access to from their setup and configuration.
Q: How is VitalCenter Online – Archival deployed and hosted?
A: VitalCenter is a software as a service application and therefore all of our infrastructure is run and maintained by Galen. Delivering the software in this way allows us to iterate and improve on the software as rapidly as possible and minimize the cost to our customers.
Q: What type of additional technical security measures have you incorporated into your solution? Could you provide more detail around that?
A: From a compliance perspective it is both HIPAA and HITECH compliant. The auditing trail specific to VCO is fully integrated and includes reporting. Data is always encrypted; at rest and in-motion. All customer data is completely isolated – there is no sharing of storage (i.e., databases). Our data center has multiple independent security and compliant certifications and attestations including:
- P-ATO (Provisional Authority to Operate)
- FERPA (Family Educational Rights and
- FIPS (Federal Information Processing Standard)
- FISMA (Federal Information Security Management Act)
- HIPAA
- ISO/IEC 27001
- SOC (Service Organization Controls)