The development of a collaborative medical modelling service: organisational and technical considerations

We describe the steps, problems, pitfalls and modifications in the development of a collaborative medical modelling service for a general hospital in the United Kingdom. We emphasise the value of having as much control as possible in the hands of clinicians so that the maximum relevant information can be obtained at minimum cost. Three-dimensional imaging, modelling and planning are now essential parts of any reconstructive surgery unit and must be adapted to make them as user friendly as possible for clinicians

Eagle-i record-level citation widget.

<p>Eagle-i record-level citation widget.</p

Record-level versioning and release-level versioning.

<p>Record-level versioning and release-level versioning.</p

Contributions and roles related to content as they correspond to identifier creation versus identifier reuse.

<p>The decision about whether to create a new identifier or reuse an existing one depends on the role you play in the creation, editing, and republishing of content; for certain roles (and when several roles apply) that decision is a judgement call. Asterisks convey cases in which the best course of action is often to correct/improve the original record in collaboration with the original source; the guidance about identifier creation versus reuse is meant to apply only when such collaboration is not practicable (and an alternate record is created). It is common that a given actor may have multiple roles along this spectrum; for instance, a given record in monarchinitiative.org may reflect a combination of (a) corrections Monarch staff made in collaboration with the original data source, (b) post-ingest curation by Monarch staff, (c) expanded content integrated from multiple sources.</p

A summary of the 10 recommendations and their direct or indirect impact on different kinds of identifier roles.

<p>A summary of the 10 recommendations and their direct or indirect impact on different kinds of identifier roles.</p

Anatomy of a web-based identifier.

<p>An example of an exemplary unique resource identifier (URI) is below; it is comprised of American Standard Code for Information Interchange (ASCII) characters and follows a pattern that starts with a fixed set of characters (URI pattern). That URI pattern is followed by a local identifier (local ID)—an identifier which, by itself, is only guaranteed to be locally unique within the database or source. A local ID is sometimes referred to as an “accession.” Note this figure illustrates the simplest representation; nuances regarding versioning are covered in Lesson 6 and <a href="http://www.plosbiology.org/article/info:doi/10.1371/journal.pbio.2001414#pbio.2001414.g005" target="_blank">Fig 5</a>.</p

Desirable characteristics for database identifiers in the life sciences.

<p>Desirable characteristics for database identifiers in the life sciences.</p