From detailed guides to online courses – resources are available to provide you with the knowledge necessary to build and integrate EHR applications.
The HIAL exposes business services that provide information from the shared resources layer. By doing this, the HIAL logically decouples the technologies and implementation details that consume EHR services from the technologies and implementation details that provide EHR services.
The benefit of this approach is that decoupled technologies are free to innovate and change without directly impacting each other or the users. Changes can be made to shared resources without impacting the users who are requesting services from point of service systems or portals. Service consumers need only request a service that is exposed through the HIAL – they need not concern themselves with how that service request is implemented.
The services exposed in the HIAL are the external interfaces to be used by point of service applications. The actual domain repositories, registries, and applications are ‘below the HIAL’ in the diagram and expose their native interfaces to it. The HIAL uses these to orchestrate the response back to the requesting system.
The HIAL exposes business services via interface contracts which will be used by point of service systems to access or put information in to the EHR. The implementation of these services will include orchestration that will involve the HIAL calling common services and accessing the registries, domain repositories and other resources in the shared resources layer, using their native interfaces.
Multiple views describe the many ways the blueprint supports EHR delivery.
From advisory consultations on blueprint alignment to standard selection, we can help you align, adopt and implement solutions.Contact Us