Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Interoperability Layer will handle the sending of all ATNA audit messages (Audit Trail), as well as provide secure interfaces for communication with external systems (Node Authentication).

Module Design

 Interface

The module will expose a single HTTP(S) endpoint and will support the aforementioned XDS.b transactions via SOAP web services. Documents will be included in SOAP messages using MTOM.

...

The module will provide new tables and functionality for storing and retrieving document metadata.

Image Added

All documents submitted to the system will get a database entry added to the registry entry document table. For repository actor transactions, such as Provide and Register Document Set.b, an entry will also be added to the registry entry document table, so as to allow for quick identification of documents. However full metadata for a document won't be added for these repository-type transactions, only the minimum required in order to identify a document. The data-model for the document registry is therefore designed to be flexible. Only a core set of fields will be required to identify a document: a document's unique id, it's content type (MIME) and the patient id. Further document metadata will be added to the document_metadata table, with the types identified via the document_metadata_type table.

Image Removed

An submissionset is used to identify documents that have been submitted together. Documents can therefore have a link to the submissionset table. Submission sets can also have metadata associated with them, provided by the submissionset_metadata and submissionset_metadata_type tables. This metadata describes the set as a whole.

 When a document is registered on the system, for example via a Register Document Set.b transaction, it will receive 

Link to Encounters

TODO How to link encounters to documents

Content Handling

For saving and querying documents, the module will make use of the functionality provided by the Content Handler module.

Folders

An XDS.b submission may contain folder object types. The module will treat folders as a document with a specific content type and will generate and process it's own document contents for use with folder types. The content is simply a JSON blob with a list of identifiers of the documents that are associated with the folder.

Tools and Resources

OpenXDS provides an open-source XDS.b implementation and is fully IHE certified. It may be possible to reuse elements of this project (perhaps as a library) for helping to implement the OpenMRS module, especially for features such as metadata validation. Another option is IHEOS. Further investigation is required to determine the extent that these tools can be reused.