Page History
...
Version | Date | Responsible | Description |
0.1 | 24.2.2012 | Systematic | Initial version. |
0.9 | 14.5.2012 | Systematic | Clarification and elaboration of Web service semantics (section 4). Clarification of attributes for user identification and explicit consent scenario. Specification of consent registration for foreign health professionals. |
0.91 | 16.5.2012 | Systematic | Clarification of how organization identification is based on SOR-code has been added to section 2.3 and 2.4. Redundant information removed from section 3.2.2. Clarification of how organization identification is based on SOR only has been corrected in section 5.5. |
1.0 | 29.6.2012 | Systematic | The user system responsibilities has been updated, SOAP-faults added, schemas updated, general improvements. Section 7 concerning WSDL added. |
1.1 | 28.11.2014 | Systematic | References to National Patient Index (NPI) removed. |
1.2 | 09.09.2016 | Systematic | Changed nsi:skscode to nsi:skskode and nsi:sorcode to nsi:sor to fit XML schema |
1.3 | 13.06.2018 | Systematic | Migrated to NSPOP SVN |
| 22.10.2018 | KIT | Document moved from Word to Confluence. Original document name was: IFS0013 Consent Administration Service Interface Description.docx | |
| 14.05.2020 | KIT | SDS-3883 Etablering af IDWS snitflade | |
| 22.10.2020 | KIT | SDS-3875 A new version of the interface has been added. This interface matches the underlying validations. |
User and User System’s Responsibility
...
Operation – ConsentRegistrationsGetV2
Name: ConsentRegistrationsGet | |
|---|---|
Description: | Retrieves descriptions of all registrations of consents applicable to given citizen. |
Input: | ConsentRegistrationsGetRequest which consists of: PatientPersonCivilRegistrationIdentifier Identification of the citizen for which consent registrations are desired |
Output: | ConsentRegistrationsGetResponse which consists of: ConsentRegistrations Collection of all active and inactive consent registrations registered for citizen in question. |
Error handling: | See section 4.7. |
Roles: | Citizen, person (on behalf of citizen) |
Prerequisites: | Both user system and user must be authenticated and authorized as described in section 4.2.1. |
Operation – ConsentAddPositiveV2
Name: ConsentAddPositiveV2 | |
|---|---|
Description: | Adds a positive active consent/active consents applicable to given citizen. |
Input: | ConsentAddPositiveV2Request which consists of: ConsentAdds Collection of descriptions of registrations of consents, that are to be added. Note that the citizen is identified in ConsentAdds. |
Output: | Nothing |
Error handling: | See section 4.7. |
Roles: | Citizen, health professional, person (on behalf of citizen). |
Prerequisites: | Both user system and user must be authenticated and authorized as described in section 4.2.1. The operation is not idempotent and on repeated calls with identical parameters, multiple identical consents will be created (see section 1.6). |
Operation – ConsentAddConstraintV2
Name: ConsentAddPositiveV2 | |
|---|---|
Description: | Adds a constraining active consent/active consents applicable to given citizen. |
Input: | ConsentAddConstraintV2Request which consists of: ConsentAdds Collection of descriptions of registrations of consents, that are to be added. Note that the citizen is identified in ConsentAdds. |
Output: | Nothing |
Error handling: | See section 4.7. |
Roles: | Citizen, health professional, person (on behalf of citizen). |
Prerequisites: | Both user system and user must be authenticated and authorized as described in section 4.2.1. The operation is not idempotent and on repeated calls with identical parameters, multiple identical consents will be created (see section 1.6). |
Operation – ConsentModifyPositiveV2
Name: ConsentModifyPositiveV2 | |
|---|---|
Description: | Updates consent(s) from the collection of consents applicable to given citizen. |
Input: | ConsentModifyPositiveV2Request which consists of: ConsentModifications Collection of descriptions of consents, that are desired modified. Note that the citizen is identified in ConsentModification. |
Output: | Nothing |
Error handling: | See section 4.7. |
Roles: | Citizen, person (on behalf of the citizen) |
Prerequisites: | Both user system and user must be authenticated and authorized as described in section 4.2.1. |
Operation – ConsentModifyConstraintV2
Name: ConsentModifyConstraintV2 | |
|---|---|
Description: | Updates consent(s) from the collection of consents applicable to given citizen. |
Input: | ConsentModifyConstraintV2Request which consists of: ConsentModifications Collection of descriptions of consents, that are desired modified. Note that the citizen is identified in ConsentModification. |
Output: | Nothing |
Error handling: | See section 4.7. |
Roles: | Citizen, person (on behalf of the citizen) |
Prerequisites: | Both user system and user must be authenticated and authorized as described in section 4.2.1. |
Operation – ConsentRevokeV2
Name: ConsentRevoke | |
|---|---|
Description: | Revokes given consent(s) from the collection of consents applicable to the provided citizen. This takes place by inactivation of the revoked consents. |
Input: | PatientConsentRevokeRequest which consists of: ConsentRevocations Collection of descriptions of consents, that are to be revoked. Note that the citizen is identified in ConsentRevocation. |
Output: | Nothing |
Error handling: | See section 4.7. |
Roles: | Citizen |
Prerequisites: | Both user system and user must be authenticated and authorized as described in section 4.2.1. |
Consent Administration Web Service Semantics
...