31.4.1MDM Operations

31.4.1.5.1Sample request for

Below is a sample request and response when using $mdm-evaluate for similarity type algorithm.

POST http://fhir.example.com/baseR4/$mdm-evaluate

Sample request body

{
	"resourceType":"Parameters",
	"parameter":[
		{
			"name":"compareTo",
			"valueString":"My tsring"
		},
		{
			"name":"compareWith",
			"valueString":"My string"
		},
		{
			"name":"algorithmType",
			"valueString":"similarity"
		},
		{
			"name":"algorithm",
			"valueString":"JARO_WINKLER"
		},
		{
			"name":"threshold",
			"valueDecimal":0.5
		}
	]
}

Sample response body

{
	"resourceType": "Parameters",
	"parameter": [
		{
			"name": "match",
			"valueBoolean": true
		},
		{
			"name": "score",
			"valueDecimal": 0.974
		}
	]
}

Below is a sample request and response when using $mdm-evaluate for matcher type algorithm.

POST http://fhir.example.com/baseR4/$mdm-evaluate

Sample request body

{
	"resourceType":"Parameters",
	"parameter":[
		{
			"name":"compareTo",
			"valueString":"Gail"
		},
		{
			"name":"compareWith",
			"valueString":"Gael"
		},
		{
			"name":"algorithmType",
			"valueString":"matcher"
		},
		{
			"name":"algorithm",
			"valueString":"CAVERPHONE1"
		}
	]
}

Sample response body

{
	"resourceType": "Parameters",
	"parameter": [
		{
			"name": "match",
			"valueBoolean": true
		}
	]
}

31.4.1.6.1How it works

For each resource in the input bundle:

1. The operation uses MDM rules to find matching resources in the repository 2. If a resource matches exactly one resource in the repository:
   • It removes the resource from the bundle
   • It updates all references to that resource in the bundle to point to the matched resource 3. If a resource matches more than one resource in the repository:
   • It throws a ResourceVersionConflictException 4. If a resource doesn't match any resources in the repository:
   • It keeps the resource in the bundle, updating references to removed resources as necessary

In addition to the above rules, if the input Bundle is a Document bundle and the first entry in the Bundle is a Composition resource, the Composition resource is removed. The operation returns a new transaction Bundle with matched resources removed and references updated. This bundle can then be submitted to the repository to create only the non-duplicate resources as determined by the MDM Rules.

31.4.1.6.2Permissions

31.4.1.6.3Limitations

• This custom operation is available for FHIR version DSTU3 and FHIR versions released after.

31.4.1.6.4Input Parameters

31.4.1.6.5Output

The operation returns a FHIR transaction Bundle with matched resources removed and references updated.

31.4.1.6.6Sample request

Below is a sample request when using $sdh.mdm-bundle-match:

POST http://fhir.example.com/baseR4/Bundle/$sdh.mdm-bundle-match

Sample request body

{
  "resourceType": "Parameters",
  "parameter": [
    {
      "name": "bundle",
      "resource": {
        "resourceType": "Bundle",
        "type": "transaction",
        "entry": [
          {
            "fullUrl": "urn:uuid:1",
            "resource": {
              "resourceType": "Patient",
              "name": [
                {
                  "family": "Smith",
                  "given": ["John"]
                }
              ],
              "birthDate": "1970-01-01"
            },
            "request": {
              "method": "POST",
              "url": "Patient"
            }
          },
          {
            "fullUrl": "urn:uuid:2",
            "resource": {
              "resourceType": "Observation",
              "status": "final",
              "code": {
                "coding": [
                  {
                    "system": "http://loinc.org",
                    "code": "8480-6",
                    "display": "Systolic blood pressure"
                  }
                ]
              },
              "subject": {
                "reference": "urn:uuid:1"
              },
              "valueQuantity": {
                "value": 120,
                "unit": "mmHg",
                "system": "http://unitsofmeasure.org",
                "code": "mm[Hg]"
              }
            },
            "request": {
              "method": "POST",
              "url": "Observation"
            }
          }
        ]
      }
    }
  ]
}

31.4.1.7.1Input

The processor takes an IBaseBundle (FHIR Bundle) as input.

31.4.1.7.2Output

The processor returns a reconciled IBaseBundle (FHIR Bundle) with matched resources removed and references updated.

31.4.1.7.3Example

The following example shows a route that reads a FHIR Bundle from a file, processes it with the MDM Bundle Match Processor, and then stores the reconciled bundle in a FHIR repository:

<route>
    <from uri="file:input/bundles?noop=true"/>
    <to uri="smile:mdm/mdmBundleMatchProcessor"/>
    <to uri="smile:persistence/bundleProcessor"/>
</route>