...
Provide a clear and brief descriptive signpost for users who are searching for metadata that may be relevant to their project.
The abstract should allow the reader to determine the scope of the data standard and accurately summarise its content.
The optimal length is one paragraph (limited to 255 characters) and effective abstracts should avoid long sentences and abbreviations where possible.
Abstracts must be different from the full description for a resource.
Note: Users will view Titles and Abstracts when searching for metadata and choosing whether to explore their content further.
...
Exchange Element
...
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 (IOPS) Guide.
Exchange Element | DAPB ISN element | IOPS Guide |
|---|---|---|
Abstract | DescriptionDescription | Sourced from guide homepage |
The Description element in the DAPB ISN often contains more characters than the 255 allowed by the Abstract, so will need to be précised before input to Abstract. More detail from the ISN Description can be entered into the Documentation.description element.
Example
ISN element
The Diabetes Record Information Standard defines the information needed to support a person’s diabetes management and care. This incorporates data recorded by health and care professionals, or the person themselves, for sharing between care providers.
IOPS guide
This Implementation Guide and the HL7® FHIR® artefacts that it references define a specification to enable the exchange of pathology laboratory test request and test result data. The specification supports FHIR versions STU3 and R4. Most of the narrative content of the specification applies to both versions of FHIR with any differences noted accordingly. Version specific FHIR artefacts (profiles, extensions, examples etc.) are referenced and/or included where appropriate.
FAQs
No questions received to date.
...