eCRNow/ConfiguringOneOrMoreERSDandOtherPlanDefinitions at master · DBCG/eCRNow · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
# 1. Running Multiple eRSD Versions concurrently #

The eCRNow App is capable of executing multiple eRSD versions concurrently. There are many scenarios where this is required. For eCR, Vendors are encouraged to use eRSDv3 and produce CDA_R31 version of the eICRs.

## Scenario 1: Organizations want to migrate to new eRSD file.

In this scenario, the same organization (HealthcareSetting) with the same FHIR Server URL will use multiple ERSD files.

The steps to enable such a configuration is

1. Disable the Old eRSD file via the API or the UI.
2. Place the new eRSD file in the folder where the eRSD files are located.
3. Restart eCRNow App.
3. Enable the new eRSD file.
4. The Old eRSD file needs to be present until all the timers that were created using the Old eRSD file get removed.
5. Finally purge the Old eRSD file when there are no more timers with the old eRSD file by using the script
"CheckTimersForERSD".

## Scenario 2: Running eCRNow App with Multiple eRSDs simultaneously for any healthcare setting.

The steps to enable such a configuration is as follows:

1. Copy one or more eRSD files to the folder where the eRSD files are location.
2. Restart the eCRNow App.
3. Enable one or more eRSD files for the Healthcare setting using the UI or the APIs.

NOTE: Enable multiple eRSD files for the same healthcare setting will result in creating multiple eICRs for the same encounter and patient combination.


## Scenario 3: Producing both FHIR and CDA eICRs for the same healthcare setting

The steps to enable such a configuration is as follows:

1. Create two folders in the location where eRSD files are located.
2. Let us name them CDA_ERSD and FHIR_ERSD, these are called repositories.
3. Copy the same eRSD file to both the folders.
4. Restart the eCRNow App.
5. Choose the CDA_ERSD repository and enable the eRSD and set the output format to CDA eICR R3.1
6. Choose the FHIR_ERSD repository and enable the eRSD and set the output format to FHIR eICR R3.1

NOTE: Enable multiple eRSD files in this fashion for the same healthcare setting will result in creating multiple eICRs (one in CDA format and one in FHIR format) for the same encounter and patient combination.

## Scenario 4: Running eRSD with other Knowledge artifacts such as eCSD (electronic Chronic Surveillance Distribution), Central Cancer Registry Reporting Plan Definition

The steps to enable such a configuration is as follows:

1. Create different folders to segregate the different knowledge artifacts in the location where the eRSD files are located.
2. Let us name them electronic_case_reporting, chronic_reporting, cancer_reporting. These are called repositories.
3. Copy the eRSD into the electronic_case_reporting, eCSD files into chronic_reporting, cancer plan definitions into the cancer_reporting.
4. Restart the eCRNow App.
5. Choose the repository and enable the plan definition and set the output format to CDA or FHIR as appropriate.

NOTE: Enable multiple plan definitons files in this fashion for the same healthcare setting will result in creating different outputs based on the plan definition.

## Scenario 3: Organizations wants to use different ERSDs for Test and Production with different Healthcare Settings.

The steps to enable such a configuration for ERSDv2 is as follows:

1. Keep the Old ERSD file as it is currently.
2. Copy the Old ERSD file into a new ERSD file. (Let us call it New ERSD).
3. In the new ERSD file, change the following:
	- Bundle.meta.versionId to a different version.
4. Place the New ERSD file into the folder where the ERSD files are located.
5. Restart the eCRNow App.
6. Enable the New ERSD for the Healthcare Setting that is needed.

The steps to enable such a configuration for ERSDv3 is as follows:

1. Keep the Old ERSD file as it is currently.
2. Copy the Old ERSD file into a new ERSD file. (Let us call it New ERSD).
3. In the new ERSD file, change the following:
	- Library.meta.versionId to a different version.
	- Library resource to be updated should have the profile set to http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-specification-library"
4. Place the New ERSD file into the folder where the ERSD files are located.
5. Restart the eCRNow App.
6. Enable the New ERSD for the Healthcare Setting that is needed.