| Oracle® Healthcare Master Person Index Working With HPD Profile Application User's Guide Release 3.0 E62313-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Healthcare Master Person Index Working With HPD Profile Application User's Guide Release 3.0 E62313-01 |
|
|
PDF · Mobi · ePub |
This chapter provides procedures on how to create, configure, and build HPD Application related projects. It also discusses the features of an HPD Project's context-sensitive menu.
This chapter includes the following sections:
HPD Application design-time support is a NetBeans plug-in. The New HPD Project wizard takes your input and creates an HPD Project along with two pre-configured Master Person Index (MPI) Projects for Individual Provider and Organizational Provider. You are able to fine-tune the matching service of the Master Person Index for Individual and Organizational Provider, and configure various properties of the HPD project. The HPD Project's Create Database dialog allows you to easily create database tables for Individual/Organizational Provider and their Relationship. Once the database table is created, you can deploy the Individual/Organizational Provider MPI Project and HPD Project to the target server using the application server administration console.
To create HPD Application related projects, perform the following:
From the NetBeans IDE, click File and then choose New Project.
The New Project dialog appears.
Choose OHMPI in the Project Category. In the Projects section of the Choose Project panel, choose HPD Profile Application and click Next.
The New HPD Project dialog appears.
In the Name and Location panel, perform the following:
In the Project Name field, type a name for your project (for example, HPD1).
In the Project Location field, browse to the path where you want to create the HPD Project.
The Project Folder field populates with the path and name of your project.
Click Finish.
Two pre-defined MPI Projects for Individual Provider and Organizational Provider are created automatically along with the HPD Project.
The two MPI Projects are named by <hpd_project_name>-IndProvider, and <hpd_project_name>-OrgProvider, respectively. The corresponding application names for these two MPI Projects are fixed to HPDIndProvider and HPDOrgProvider, respectively. Note the difference between the project name and application name. Later on, the two MPI Project's application names are needed to configure various Application Server resources.
Note:
These two MPI Projects have to be built and deployed separately along with the HPD Project.You can configure several features of the Master Person Index to customize how data is matched and processed in the Individual/Organizational Provider MPI Project. The type and quality of data stored for a provider varies from system to system and from organization to organization. The Master Person Index takes this into account and lets you to tailor the processing for your specific data requirements. For example, you may know that some systems contain more accurate data than others. You can weight those systems higher when determining which values will populate the single best record (SBR). Also, some fields might contain more accurate data than others and would thus be given a higher match weight than other less accurate fields.
You can configure the following components of the Master Person Index:
Provider demographic queries, matching queries, and queries performed from the MIDM.
Standardization and matching rules, including which fields to standardize, which fields to match, a range of match weights to assign to each field, and the type of algorithm to use to match each field.
Filters for match results (for example, you can configure the Master Person Index to ignore default values).
The single best record and how it is formed.
The appearance of the Master Index Data Manager (MIDM).
Field validations.
In addition, you can customize logic for the underlying process of the Master Person Index. For complete information on configuring the Master Person Index, see Oracle Healthcare Master Person Index Configuration Guide.
If you modify the configuration of the Individual/Organizational Provider MPI Project, you need to do the following:
Clean the Individual/Organizational Provider MPI Project.
Generate Master Index Files.
Build the Individual/Organizational Provider MPI Project.
Deploy the Individual/Organizational Provider MPI Project.
Note:
You cannot modify the object model in the Individual/Organizational Provider MPI Project.The context-sensitive menu that you access by right-clicking an HPD Project in the left panel of NetBeans IDE provides you with the necessary tools to manage the HPD Project.
Build: Builds an HPD Project and generates its artifacts.
Clean and Build: Removes generated artifacts from an HPD Project and then rebuilds the project and generates new artifacts.
Clean: Removes generated artifacts from an HPD Project.
Create Database: Opens the Create Database dialog. For information, see Creating MPI and HPD Database Tables Automatically).
Set as Main Project: Sets the selected HPD Project as the main project.
Open Required Project: Opens the associated Individual/Organizational Provider MPI Projects.
Close: Closes the HPD Project.
Properties: Opens the Project Properties dialog, where you can change various runtime HPD configurations.
Before building HPD Project, you need to configure it. This includes:
Editing the following configuration file to change HPD service properties.
services.properties
Following is a list of user-configurable properties for HPD Project. You need to manually edit the services.properties file before building the HPD Project.
Note:
If you have to change any of these configurations after you build and/or deploy the HPD project, you can always rebuild and redeploy the HPD project after updating the
services.properties file. Alternatively, you can create a runtime property file called hpd.properties under the <app_server_domain>/config/ohmpi directory. The properties defined in the runtime hpd.properties overwrite the properties defined in services.properties at build time.Open the services.properties file under the HPD Project's Configuration Files from within NetBeans IDE and make the appropriate edits.
base_dn=o=ORACLE,dc=HPD
ohmpi_assigning_authority_name=OHMPIAssigningAuthority
sole_source_system=IHEAssigningAuthority
fail_on_unknown_attribute_in_query=false
check_base_dn=false
use_ohmpi_assigning_authority_in_query_response=false
support_implicit_federation=false
federation_self_directory_id=
federation_self_directory_uri=
federated_directories=
The following table provides detailed explanations to these properties:
| Property Name | Property Description |
|---|---|
base_dn |
This is the Base DN for all the objects in the directory.
As per IHE's HPD specification,
|
ohmpi_assigning_authority_name |
OHMPI's Assigning Authority Name. This is the namespace to scope all the EUIDs assigned by OHMPI. |
sole_source_system |
Name of the single source system in HPD Feed. This is to support a special use case of Provider Information Directory where there is only a single source system for Individual/Organizational Providers.
See |
fail_on_unknown_attribute_in_query |
Whether to fail on unknown attribute in HPD Query. |
check_base_dn |
Whether to verify Base DN in HPD Query. |
use_ohmpi_assigning_authority_in_query_response |
Whether to use OHMPI Assigning Authority for DNs in HPD Query response.
|
support_implicit_federation |
Whether to perform implicit federation when the Provider Information Consumer is not federation-aware. In other words, if the HPD Query request does not contain federation related control element, whether the Provider Information Directory should try to perform federation anyway. |
federation_self_directory_id |
A unique global identifier to identify this Provider Information Directory for federation. |
federation_self_directory_uri |
Service endpoint of this Provider Information Directory for federation. |
federated_directories |
A list of federated directory entries delimited by '$'. Each federated directory entry is in the format of DIRECTORY_ID^DIRECTORY_URI[^DIRECTORY_BASE_DN].
For example:
Leave the value of this property blank if there is no federated directory. |
This section provides the steps to build an HPD Project along with the Individual/Organizational Provider MPI Project.
In the left panel of NetBeans IDE, right-click the Individual Provider MPI Project icon (for example, HPD1-IndProvider).
The context-sensitive menu appears.
Run Generate Master Index Files first.
To build the Individual MPI Project, click Build on the context-sensitive menu.
When you build the Individual Provider MPI Project, the following artifact is created:
<hpd_project_name>-IndProvider.ear: This is the deployable file for the Individual Provider MPI Project.
In the left panel of NetBeans IDE, right-click the project icon (for example, HPD1-OrgProvider).
The context-sensitive menu appears.
Run Generate Master Index Files first.
To build an Organizational MPI Project, click Build on the context-sensitive menu.
When you build the Organizational Provider MPI Application project, the following artifact is created:
<hpd_project_name>-OrgProvider.ear: This is the deployable file for the Organizational Provider MPI Project.
In the left panel of NetBeans IDE, right-click the HPD Project icon (for example, HPD1).
The context-sensitive menu appears.
To build HPD Project, click Build on the context-sensitive menu.
When you build the HPD Application project, the following artifact is created:
<hpd_project_name>.ear: This is the deployable file for the HPD Project.
|
 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|