v2+ Details - Local Development build (v0.3.2). See the Directory of published versions

UI

An important aspect is the way the standard is presented. As mentioned already on the one hand the standard should contain the same amount of information and specifity as before. On the other hand, it is questionable what should belong the base/core standard, and what is in the end some kind of base common profile. On the webpage www.hl7.eu/refactored/index.html they are called “Core Framework” for the first, and “Base Standard Profile” for the latter.

For convenience, this is currently presented as:

This way of representing it allows for seeing everything, i.e. the “standard” supporting the same specifity as before. The profile on the right of the blue line must be added to the left, possibly leading to overwrite or add to it. In this example, the cardinality of ORC-1 is further constrained. And the vocabulary adds some value sets and codesystems if necessary. (Note: for ORC-1 the VS and CS must be moved to the left!!!!)

However, it could also be separated into distinct pages. That is just a matter of programming the generator. The next mockup shows the pure base standard alone:

The third screenshot demonstrates how it would look like, if the final view is presented. This is the most common base profile then. As a consequence, one would not see the overwrite of the cardinality any more, unless this is highlighted somehow.

Beside the option to present everything in one page, as it is today, the contents can be separated by different pages, e.g. on tabs, or the generation into totally separated websites, i.e. IGs.

Unfurtunately, that results in losing oversight and being forced to navigate to different pages, without seeing the overlap or differences.

Furthermore, the way the current page is presented also allows for using scripts to move content around, so that the different view presented above can be realized - just according to individual needs.