CDS resource

[ErikSundvall]

Either as a part of the main REST spec or as an appendix we might want to have a look at specifying management and execution fo CDS rules via REST. There are already implementation experiences from Marand and DIPS that could give good input to discussion.

[bjornna]

For CDS we have divided into two different resources.

• GDL resource with standard CRUD operations
• CDS resource with GET and POST operations to execute defined GDLs.

The GET operation is defined as:

GET //cds/{ehrId}/{guideId}

The POST operation have the following payload:

{ "guideId": "string", "ehrIds": [ "string" ], "tagScope": { "tags": [ { "values": [ "string" ], "tag": "string" } ] }, "partitionBy": { "tag": "string", "limit": 0 } }

If you would like to test the resultset you may access the resource below which runs a BMI GDL on a given EHR.

http://arenaehr.dips.no:9000/api/v1/cds/5ffe875c-aa91-8141-96ca-9aec50ea7368/BMI.Calculation.v.1

[bjornna]

I have added CDS support both in knowledge and runtime in pull request: https://github.com/openEHR/specifications-ITS/pull/26

@ErikSundvall : Would that be Ok to complete this issue?