This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Logical Model SourceAndNotation
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="SourceAndNotation"/> <url value="{http://www.omg.org/spec/CTS2/1.1/Core}SourceAndNotation"/> <name value="SourceAndNotation"/> <display value="CTS2.SourceAndNotation"/> <status value="draft"/> <publisher value="Generated by Xsd-to-FHIR"/> <contact> <name value="Visit the Github repository for more information"/> <telecom> <system value="other"/> <value value="https://github.com/cts2/CTS2-to-FHIR"/> </telecom> </contact> <date value="2016-02-08T19:11:02-07:00"/> <description value="A description of the source from which the ResourceVersionDescription was derived. When possible, SourceAndNotation should include a reference to the actual source document from which it was derived. As an example, if the resource was derived from the W3C Wine Ontology, the URI http://www.w3.org/TR/2003/CR-owl-guide-20030818/wine would unambiguously name the document. In the cases, however, when a definitive source document is not available, a textual description should be provided, instead, in sourceAndNotationDescription. Where possible, the ontology language and ontology syntax should also be provided. In the case of the Wine Ontology above, the ontology language would be http://www.w3.org/2002/07/ow l# (OWL) and the syntax would be application/rdf+xml."/> <fhirVersion value="1.4.0"/> <kind value="logical"/> <abstract value="false"/> <snapshot> <element> <path value="SourceAndNotation"/> <short value="SourceAndNotation"/> <definition value="A description of the source from which the ResourceVersionDescription was derived. When possible, SourceAndNotation should include a reference to the actual source document from which it was derived. As an example, if the resource was derived from the W3C Wine Ontology, the URI http://www.w3.org/TR/2003/CR-owl-guide-20030818/wine would unambiguously name the document. In the cases, however, when a definitive source document is not available, a textual description should be provided, instead, in sourceAndNotationDescription. Where possible, the ontology language and ontology syntax should also be provided. In the case of the Wine Ontology above, the ontology language would be http://www.w3.org/2002/07/ow l# (OWL) and the syntax would be application/rdf+xml."/> <min value="0"/> <max value="*"/> </element> <element> <path value="SourceAndNotation.sourceAndNotationDescription"/> <name value="sourceAndNotationDescription"/> <short value="a textual description of where the specified resource version was derived from"/> <definition value="a textual description of where the specified resource version was derived from. This parameter must be supplied if a reasonable PersistentURI for the source document is not available."/> <min value="0"/> <max value="1"/> <type> <code value="String"/> </type> </element> <element> <path value="SourceAndNotation.sourceDocument"/> <name value="sourceDocument"/> <short value="a persistent URI that references the document from which the resource version was derived"/> <definition value="a persistent URI that references the document from which the resource version was derived. This URI may be resolvable to a digital resource or may be the name of a book, publication or other external document."/> <min value="0"/> <max value="1"/> <type> <code value="PersistentURI"/> </type> </element> <element> <path value="SourceAndNotation.sourceLanguage"/> <name value="sourceLanguage"/> <short value="the formal language, if any, that the source for the resource version is expressed in"/> <definition value="the formal language, if any, that the source for the resource version is expressed in. Examples include Common Logic, OWL, OWL-DL, CLAML, etc."/> <min value="0"/> <max value="1"/> <type> <code value="OntologyLanguageReference"/> </type> </element> <element> <path value="SourceAndNotation.sourceDocumentSyntax"/> <name value="sourceDocumentSyntax"/> <short value="the syntax of the source of the resource version, if known"/> <definition value="the syntax of the source of the resource version, if known. Examples might include rdf/xml, Turtle, Manchester Syntax, CSV, etc."/> <min value="0"/> <max value="1"/> <type> <code value="OntologySyntaxReference"/> </type> </element> </snapshot> </StructureDefinition>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.