Configuration

Database requirements

The code values that indicate a particular line of service are checked with a database query, just as the Type 5 code values are checked.

The Pack for Healthcare does not come with a packaged database application. To use Type 6 validation, you must have a Database server accessible that has MongoDB interface 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 the line of service for the Type 6 rules that are implemented in the Pack for Healthcare. If these values need to be updated between Pack releases, they 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 utilities map uses or by using any of the UI tooling supported by your database server.

If you need to modify the values in the code sets, the key difference in Type 6 tables is that if the value that indicates a particular line of service is represented by two different elements or subelements, the values are concatenated with an underscore in the table.

{

"code" : "HC_A0170"

"description" : "Transport parking fees/tolls",

“startDate" : "1982-01-01"

}