Dependencies

Completion Guidance

Section: Documentation (2)
Completion: Required
Minimum number of entries allowed: 0
Maximum number of entries allowed: Multiple
Syntax restrictions: Header and Named link

  • A collection of relevant dependencies, such as terminologies / ontologies / controlled vocabularies or standardised data models that this resource is dependent on.

  • NOTE: you should only be able to link to another resource within the directory

  • This element is composed of

    • a Header (0..1) - Text that will appear above the named link(s). It has an an AbstractText datatype, which takes characters between 5 and 255 in length.

    • a Name (1..1) for the dependency

    • a url (0..1) with a url datatype

    • an Explanation (0..1) with a String datatype, which is an expanded explanation about the link

Mappings

The table below shows the element mappings between the Exchange data model, the Data Alliance Partnership Board (DAPB) Information Standard Notice (ISN) and the Interoperability Standards Team Guide.

Note that where there is no direct mapping to the DAPB ISN, the editor will need to glean this information from reading through all documentation for the standard.

Exchange Element

DAPB ISN element

IOPS guide

Exchange Element

DAPB ISN element

IOPS guide

Dependency

No direct mapping

To be decided

Example

https://theprsb.org/core-information-standard-v2-0/

UK Core Implementation Guide 1.0.0 - STU1 - NHS Standards Directory

NHS Standards Directory

https://www.datadictionary.nhs.uk/

UK Core Implementation Guide 1.0.0 - STU1 - NHS Standards Directory

FAQs

No questions received to date.

If you need further clarification, feel free to raise a support desk ticket.