This service should be used to create a patient within a hub. It can also be used to update the information about a patient.
This service allows a healthcare party to ask to another healthcare party to publish documents related to a patient. This service is intended to be used, for instance, for documents whose reporting date is anterior to the consent of the patient.
This service allows a hub to ask to another hub to propagate the request to the hcparty owner in order to publish documents related to a patient. This service does not allow a hub to ask information to an hcparty owner outside of the network covered by the target hub.
This service should be used to revoke access right on a transaction within a hub. It is possible to revoke a specific access right or all access right associated on the transaction.
This service should be used to revoke the consent of an healthcare party within a hub.
This service should be used to revoke a therapeutic link between a patient and an healthcare party within a hub.
This service should be used to “unpublish” a given transaction.
This service should be used to get the list of transaction accesses for a given patient.
This service should be used by a hub to retrieve the list of transaction accesses for a given patient.
This transaction is related with the eBirth webservices. It has been defined by FedICT. This transaction corresponds to elements of the birth notification related to the mother. The transaction content has been jointly defined by the FPS Economy, the 3 Belgian communities (Brussels, Flemish and French), the FPS Health and CEPIP as part of the description of model I statistical data, established by the Royal Decree of 14 June 1999, and implemented by FedICT for the eBirth project.