Setup for Design Studio V1-based map executions
Procedure
- Open map compliance_check.mms or hipaa_data_compliance under hipaa/maps.
- Build all maps for specific platform Linux. All maps will be created with a .lnx extension.
- With the exception of the compliance_check.lnx or hipaa_data_compliance.lnx, rename all other maps from .lnx to .mmc.
-
Under the container /tmp/itx-rs/data/maps directory,
create a directory structure, and copy compiled maps to
/maps directory and data files (with UNIX based line
endings):
/tmp/itx-rs/data/maps/hipaa/tmp/itx-rs/data/maps/hipaa/maps/tmp/itx-rs/data/maps/hipaa/data
-
Additional steps needed for running Type 5 validation in hipaa data compliance
include updates and references to the resource registry files found in
hipaa/examples/code_sets.
- Ensure that the host value in the hipaa_code_set.mrn file points to a MongoDB server that is accessible from the container, and that server includes the hipaa_code_sets database with external code set collections/values that are to be validated (these can be loaded with the maps in hipaa/examples/code_sets).
- Copy both files to an accessible directory, such as /tmp/itx-rs/data/maps/code_sets.
-
Add the .mrc file to the
config.yaml, similar to the following:
rest: inbound: ports: http: 8080 https: 8443 mode: fenced resourceRegistryFile: "/data/maps/code_sets/hipaa_code_set.mrc"
-
To execute compliance_check through command line:
-
With the default input files:
curl -X PUT -d "" "http://localhost:8080/tx-rest/v1/itx/maps/direct/ hipaa.maps.compliance_check" -
To override input card 2:
curl -X PUT -d "" "http://localhost:8080/tx-rest/v1/itx/maps/direct/ hipaa.maps.compliance_check?input=2;FILE;../data/inputfile.dat"
-
With the default input files:
-
To execute compliance_check using Swagger UI:
- In the path field, enter the path: .hipaa.maps.compliance_check
- In the input field, specify the input data for card 2 from the file: input=2;FILE;../data/all_hippa_5010_transaction
- In the return field, specify audit
Note:If you need to apply configurable rules to the HIPAA compliance process, be aware that this step can only be done on Windows prior to building the compliance_check maps, and the configurable_rules map does not need to be ported.