Configuring Profile to Use

Activating Generic Profile

  1. If the HSO profile has been activated, it can be deactivated by finding the value <value>iMDsoft.Fhir.R4.Profiles.HSO</value> and changing it to <value />. If it has not been activated, then nothing needs to be changed in the config.

Activating HSO Profile

  1. After the Audit Event installation and the separate HSO Profile installation, edit the web.config file.

  2. Search for the setting named "ActiveFhirProfiles" and add the following under that area: <value>iMDsoft.Fhir.R4.Profiles.HSO</value> (HSO is the name of the profile.)

  • Example:
    <iMDsoft.Fhir.R4.Profiles.Common.Properties.Settings>
      <setting name="ActiveFhirProfiles" serializeAs="String">
        <value>iMDsoft.Fhir.R4.Profiles.HSO</value>
      </setting>
    </iMDsoft.Fhir.R4.Profiles.Common.Properties.Settings>
  1. If the config is not adjusted as above, then the HSO profile will not be used (and the generic profile will be used instead.)

Additional Profile Settings

Generic Profile Configuration

When the Generic profile is in use, most of the coding systems are hardcoded, except for a few systems which can either return a default system in the response, or be overridden to return another string.

Overriding Default Coding Systems

  1. Edit the web.config file, and find the section titled <appSettings>

  2. Enter the a config key name and a default html according to the following example, replacing the value with the desired system name.

    Note that if multiple APIs are installed, the same key will be shared across them if supported. (For example, setting the MR# system will affect both MedicationDispense and also AuditEvent.)

    <appSettings>
      <add key="UsersLogin" value="Fill in user login system name" />
      <add key="DepartmentsExternalCode" value="Fill in Department system name" />
      <add key="MRNumber" value="Fill in MR number system name" />
    </appSettings>
  1. Now the returned resources should have the coding systems configured. Any unconfigured ones should have the default systems instead.

Default systems, configuration keys, and affected fields:

Object path Config Key Name Default if not configured
AuditEvent.agent.who.identifier.system UsersLogin http://www.imd-soft.com/CodingSystem/Users/Login
AuditEvent.source.observer.identifier.system DepartmentsExternalCode http://www.imd-soft.com/CodingSystem/Departments/ExternalCode
AuditEvent.entity.what.identifier.system MRNumber http://www.imd-soft.com/CodingSystem/Patients/MRNumber

HSO Profile Configuration

Configuring MRG Attribute and Observer System

  1. Create an attribute with a free text property called HF_Organisasjonsnummer and assign it to MRGs. The attribute name doesn’t matter - only the attribute property name is important.

  2. Fill in a value for the alphabetically first MRG.

  3. Edit the config file and add the MrgAttributeName setting and value as specified below to the API Properties Settings.

    <applicationSettings>
      <iMDsoft.API.Properties.Settings>
          <setting name="MrgAttributeName" serializeAs="String">
            <value>HF_Organisasjonsnummer</value>
          </setting>
    </iMDsoft.API.Properties.Settings>

Configuring MR Number (encounter) system

  1. Edit the web.config file, and find the section titled

  2. Enter the a config key name and a default html according to the following example, setting the value as below.

    Note that if multiple APIs are installed, the same key will be shared across them if supported. (For example, setting the MR# system will affect both MedicationDispense and also AuditEvent.)

    <appSettings>
      <add key="MRNumber" value="urn:oid:2.16.578.1.12.4.1.4.1" />
    </appSettings>

Now the returned resources should have the coding systems configured. Any unconfigured ones should have the default settings instead.