Configuration

Database requirements

The Pack for Healthcare does not come with a packaged database application. To use the Code Value Type 5 validation, you must have a Database server accessible that has MongoDB interface or JDBC support for queries and load.

The maps provided in the External Code List Utilities example, the primary map being load_all_code_sets, can be run to load the code set collections with the documents that represent the list of allowed code values for that code set. There may be code sets that are updated between Pack releases, and the values need to be updated in the database. Updates for individual code values, to add/remove values, or to add a start date or end date can be done by reloading a full updated code list in the JSON format that the utility map uses or using any of the UI tooling supported by your database server.

The Pack for Healthcare does not provide JSON files to load all the code sets listed in the HIPAA Implementation guides. In some cases, due to the size of the code set if all data values were included, such as the ISO Country Code set 5, we do not include the full set. Users can generate the JSON files directly to include only those values they expect to be in the transactions being processed. In some cases, the data for the code set must be separately licensed.

Note on terminology for NoSQL databases, and how code set support is implemented for the Pack for Healthcare: All the code source sets will be loaded into one Database (default used is hipaa_code_sets). A collection is defined for each code source. The collection contains multiple documents, with each document containing an individual code source value, with a description and optional start/end dates.

The document format for each code set entry must conform to the JSON structure in code_set_template.json, provided in the External Code List Utilities example.