Many of our customers are currently more or less directly involved in setting up electronic patient files. For that reason, the idea of introducing a JiveX Healthcare Content Management system (HCM) is barely on their radar. But that's a mistake. Because in its full expansion, HCM represents the electronic file. Why that is the case and how to kill two birds with one stone, we reveal to you in this fourth episode of our series of blogs "HCM SPELLED OUT".
Just think about it: HCM is the place where potentially all medical data is brought together, on a patient- and/or case-related basis. The system provides the necessary tools for this, such as for data integration and format harmonization, together with the matching infrastructure, e.g. the Multiformat Viewer and the Archive component. Let's assume that a facility makes full use of the opportunities brought about through that and allows all data - from the finding letter to the ECG to the moving image from endoscopy - to flow into HCM via interfaces. Once there, the data is categorized using the previously-defined file plan and stored: So what does that result in, if not an electronic patient file?
Clear path for portals and national infrastructures
As a central collection of medical data, HCM can not only assume the function of a facility-internal electronic file, but also forms the basis for cross-facility data exchange. Whether this involves regional medical networks, portals or national files is immaterial. Because on its path to the HCM system, the data is already converted into recognized standard formats, so that it can be effortlessly extracted from the HCM and fed into other infrastructures.
And HCM can do even more. A quick look at the neighboring countries of Austria and Switzerland reveals that national patient files can be very effectively implemented using IHE profiles. In these two actual instances, but also on many other portal solutions, the IHE-XDS profiles are used. They govern the exchange of the respective data between four actors: the document or image source, the repository, the registry and the consumer.
As the central collection point for all medical data, HCM can effortlessly assume the role of the document or image source - in other words, the in-house source archive - and that of the repository (storage location of the data to be exchanged). In such a scenario, the Multiformat Viewer serves as consumer, via which even "outside" data (i.e. from outside the facility) can be viewed, if the corresponding authorization is held.