Generated Narrative: StructureDefinition software-citation Name Flags Card. Type Description & Constraints Citation 0..* Citation A description of identification, location, or contributorship of a publication (article or artifact) Interfaces Implemented: MetadataResource #xD; citedArtifact #xD; identifier 0..* Identifier Unique identifier. May include DOI, FOI, Database Accession Number, etc #xD; publicationForm #xD; publishedIn #xD; type 0..1 CodeableConcept Kind of container (e.g. Periodical, database, or book) #xD; identifier 0..* Identifier Unique identifier. #xD; title 0..1 string Title of the database #xD; Slices for classification 1..* BackboneElement The assignment to an organizing scheme Slice: Unordered, Open by value:type.coding #xD; classification:knowledgeArtifactType S 1..1 BackboneElement The assignment to an organizing scheme #xD; type #xD; coding 1..1 Coding Code defined by a terminology system Required Pattern: At least the following #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/cited-artifact-classification-type #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: knowledge-artifact-type #xD; display 1..1 string Representation defined by the system Fixed Value: Knowledge Artifact Type #xD; Slices for classifier 1..* CodeableConcept The specific classification value Slice: Unordered, Open by value:coding #xD; classifier:software S 1..1 CodeableConcept The specific classification value #xD; coding 1..1 Coding Code defined by a terminology system Required Pattern: At least the following #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/citation-artifact-classifier #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: executable-app #xD; display 1..1 string Representation defined by the system Fixed Value: Executable app #xD; classification:definedInText 0..* BackboneElement The assignment to an organizing scheme #xD; type #xD; coding 1..1 Coding Code defined by a terminology system Required Pattern: At least the following #xD; system 1..1 uri Identity of the terminology system Fixed Value: https://fevir.net/resources/CodeSystem/179423 #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: defined-in-text #xD; display 1..1 string Representation defined by the system Fixed Value: Defined in text #xD; Documentation for this format
HL7 International / Clinical Decision Support
Profile of Citation for Evidence Based Medicine IG. The SoftwareCitation Profile is used for citations of executable code.
A description of identification, location, or contributorship of a publication (article or artifact)
The Citation Resource enables reference to any knowledge artifact for purposes of identification and attribution. The Citation Resource supports existing reference structures and developing publication practices such as versioning, expressing complex contributorship roles, and referencing computable resources.
Name should be usable as an identifier for the module by machine processing applications such as code generation
name.exists() implies name.matches('^[A-Z]([A-Za-z0-9_]){1,254}$')
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. Contained resources may be a resource type defined in the FHIR specification, or an [additional resource](http://build.fhir.org/resource.html#additional).
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://build.fhir.org/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Canonical identifier for this citation record, represented as a globally unique URI
An absolute URI that is used to identify this citation record when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this summary is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the summary is stored on different servers.
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.
Allows the citation record to be referenced by a single globally unique identifier.
URL should not contain | or # - these characters make processing canonical references problematic
Identifier for the citation record itself
A formal identifier that is used to identify this citation record when it is represented in other formats, or referenced in a specification, model, design or an instance.
Use this element if you need to identify the citation record independently from identifying the cited artifact.
Allows externally provided and/or usable identifiers to be associated with this citation record.
The identifier that is used to identify this version of the citation record when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the citation record author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.
This is a business version label used for display in understanding the formal version of the citation record, not a resource version id or technical version number for an archival system. There may be different citation record instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the citation record with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](http://build.fhir.org/resource.html#bv-format).
Indicates the mechanism used to compare versions to determine which is more current.
If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 is newer, and a 0 if the version ordering can't successfully be determined.
Name for this citation record (computer friendly)
A natural language name identifying the citation record. This name should be usable as an identifier for the module by machine processing applications such as code generation.
The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
Support human navigation and code generation.
Name for this citation record (human friendly)
A short, descriptive, user-friendly title for the citation record.
This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc. Use this element if you have a need for naming the citation record for human use, such as a display name for the citation record that is used when selecting citations from a list.
The status of this summary. Enables tracking the life-cycle of the content.
Allows filtering of summaries that are appropriate for use versus not. Use "active" when the citation record is the version for others to actively use, "draft" while you are developing the content, and "retired" when this record should no longer be used for any purpose. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).
Allows filtering of citation records that are appropriate for use versus not.
This is labeled as "Is Modifier" because applications should not use a retired {{title}} without due consideration
A Boolean value to indicate that this citation record is authored for testing purposes (or education/evaluation/marketing) and no version of this resource will ever be intended for genuine usage.
Allows filtering of citation records that are appropriate for use versus not.. Experimental resources might include example instances in implementation guides, instances created solely for testing purposes, etc. If experimental is 'true' for any version of a resource, it should be true for all versions of the resource. (If experimental changes, then it is being misused or a resource that was never intended for real-world use has unexpectedly changed its purpose.). Experimental resources are not expected to be stable and may well have breaking changes without a corresponding change to the 'version' element.
Enables experimental content to be developed following the same lifecycle that would be used for a production-level citation record.
If absent, this resource is treated as though it is not experimental.
The date (and optionally time) when the citation record was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the citation record changes.
The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the citation record. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).
Who authored or created the citation record.
The Citation.author element is structured to support a name (with a string datatype) and contact point information for the author/creator, and is not structured to support unique identifiers for the author. If detailed contributorship data is needed for the authorship of the citation record, then one can create a Citation Resource for the Citation Resource.
The publisher of the citation record, not the publisher of the article or artifact being cited
The name of the organization or individual that published the citation record.
Usually an organization but may be an individual. The publisher (or steward) of the citation record is the organization or individual primarily responsible for the maintenance and upkeep of the citation record. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the citation record. This item SHOULD be populated unless the information is available from context.
Helps establish the "authority/credibility" of the citation record. May also allow for contact.
Contact details for the publisher of the citation record
Contact details to assist a user in finding and communicating with the publisher.
May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).
Natural language description of the citation
A free text natural language description of the citation from a consumer's perspective.
This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the citation as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the citation is presumed to be the predominant language in the place the citation was created).
The context that the citation record content is intended to support
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate citation record instances.
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
Assist in searching for appropriate content.
Intended jurisdiction for citation record (if applicable)
A legal or geographic region in which the citation record is intended to be used.
It may be possible for the citation record to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)
Explanation of why this citation is needed and why it has been designed as it has.
This element does not describe the usage of the citation. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this citation.
Use and/or publishing restrictions for the citation record, not for the cited artifact
Use and/or publishing restrictions for the citation record, not for the cited artifact.
Copyright holder and year(s) for the ciation record, not for the cited artifact
A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved').
The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.
Defines the content expected to be rendered in all representations of the artifact.
When the citation record was approved by publisher
The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage.
The 'date' element may be more recent than the approval date because of minor changes or editorial corrections. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).
When the citation record was last reviewed by the publisher
The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.
If specified, this date follows the original approval date. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).
Gives a sense of how "current" the content is. Resources that have not been reviewed in a long time may have a risk of being less appropriate/relevant.
When the citation record is expected to be used
The period during which the citation record content was or is planned to be in active use.
The effective period for a citation record determines when the content is applicable for usage and is independent of publication and review dates. For example, a citation intended to be used for the year 2016 might be published in 2015. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).
Allows establishing a transition before a resource comes into effect and also allows for a sunsetting process when new versions of the citation record are or are expected to be used instead.
Who entered the data for the citation record
Who entered the data for the citation record.
The Citation.recorder element is structured to support a name (with a string datatype) and contact point information for the recorder, and is not structured to support unique identifiers for the recorder. If detailed contributorship data is needed, then one can create a Citation Resource for the Citation Resource.
Who edited or revised the citation record.
The Citation.editor element is structured to support a name (with a string datatype) and contact point information for the editor, and is not structured to support unique identifiers for the editor. If detailed contributorship data is needed for the editing of the citation record, then one can create a Citation Resource for the Citation Resource.
The Citation.reviewer element is structured to support a name (with a string datatype) and contact point information for the reviewer, and is not structured to support unique identifiers for the reviewer. If detailed contributorship data is needed for the review of the citation record, then one can create a Citation Resource for the Citation Resource. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).
The Citation.endorser element is structured to support a name (with a string datatype) and contact point information for the endorser, and is not structured to support unique identifiers for the endorser. If detailed contributorship data is needed for the endorsement of the citation record, then one can create a Citation Resource for the Citation Resource. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).
A human-readable display of key concepts to represent the citation
A human-readable display of key concepts to represent the citation.
All FHIR elements must have a @value or children or both
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Format for display of the citation summary
Format for display of the citation summary.
The human-readable display of the citation summary
The human-readable display of the citation summary.
Use this element if you need to classify the citation record independently from classifying the cited artifact.
The kind of classifier (e.g. publication type, keyword)
The kind of classifier (e.g. publication type, keyword).
Used for general notes and annotations not coded elsewhere
Used for general notes and annotations not coded elsewhere.
Use this if needed for reporting the state or status of the citation record, NOT FOR reporting the state or status of the cited article.
An effective date or period for a status of the citation record
The state or status of the citation record paired with an effective date or period for that state.
The state or status of the citation record (that will be paired with the period).
Whether the status date is actual (has occurred) or expected (estimated or anticipated).
For an instance, place the same value in both start and end elements.
Relationships that this Citation has with other FHIR or non-FHIR resources that already exist.
documentation | justification | predecessor | successor | derived-from | depends-on | composed-of | part-of | amends | amended-with | appends | appended-with | cites | cited-by | comments-on | comment-in | contains | contained-in | corrects | correction-in | replaces | replaced-with | retracts | retracted-by | signs | similar-to | supports | supported-with | transforms | transformed-into | transformed-with | specification-of | created-with | cite-as | summarizes
The type of relationship to the related artifact.
The artifact that is related to this Citation
The artifact that is related to this Citation Resource.
The article or artifact being described.
Unique identifier. May include DOI, FOI, Database Accession Number, etc
A formal identifier that is used to identify the cited software when it is represented in other formats, or referenced in a specification, model, design or an instance.
This element will contain unique identifiers that support de-duplication of citations. Commonly used identifiers for study citations include digital object identifier (DOI), PubMed ID (PMID), and PubMed Central ID (PMCID). To maintain interoperability, the suggested identifier.system values to use for these 3 identifiers are: DOI = "https://doi.org" PMID = "https://pubmed.ncbi.nlm.nih.gov" PMCID = "https://www.ncbi.nlm.nih.gov/pmc/"
Allows externally provided and/or usable identifiers to be associated with the cited artifact.
Identifier not unique to the cited artifact. May include trial registry identifiers
A formal identifier that is used to identify things closely related to the cited artifact.
May include trial registry identifiers, e.g. NCT04372602 from clinicaltrials.gov. This related identifier would not be used as a unique identifier for the cited artifact itself. Multiple published articles (each with their own unique identifier) may relate to the same study record in a research registry. Commonly used related identifiers for study registries include ClinicalTrials.gov identifier (NCTId) and PROSPERO identifier (used for registration of systematic reviews). To maintain interoperability, the suggested identifier.system values to use for these 2 identifiers are: ClinicalTrials.gov = "https://clinicaltrials.gov" PROSPERO = "https://www.crd.york.ac.uk/prospero/"
Allows externally provided and/or usable identifiers to be associated with this the cited artifact.
Use this element when citing an artifact from a potentially unstable source, such as a webpage, to note the date (and time) the source was accessed.
The defined version of the cited artifact
The defined version of the cited artifact.
This is a business version label used for display in understanding the formal version of the cited artifact, not a resource version id or technical version number for an archival system.
An effective date or period for a status of the cited artifact
An effective date or period, historical or future, actual or expected, for a status of the cited artifact.
A definition of the status associated with a date or period.
The title details of the article or artifact
The title details of the article or artifact.
Used to express the reason for or classification of the title.
Used to express the specific language of the title.
The abstract may be used to convey article-contained abstracts, externally-created abstracts, or other descriptive summaries.
Used to express the reason for or classification of the abstract.
Used to express the specific language of the abstract.
There is also a copyright element in the publicationForm element, so this copyright element is intended for copyright of the abstract.
The component of the article or artifact
The component of the article or artifact.
Citation for the primary version and complete form of the cited artifact
Citation for the primary version and complete form of the cited artifact.
When referencing a baseCitation, one may inherit any data from the referenced Citation Resource and consider any data in the current Citation Resource as superceding to be version-specific or part-specific. For example, the part-specific Citation may have additional contributorship data that supercedes the contributorship data for the full citation when there is a need to uniquely report the contributorship for an image or supplement associated with the fuller citation record.
The artifact related to the cited artifact
The artifact related to the cited artifact.
The citedArtifact.relatesTo element uses a BackboneElement instead of the RelatedArtifact Datatype to enable use of an extended value set for the required code for the type of relationship.
Provides additional classifiers of the related artifact.
A short label that can be used to reference the related artifact from elsewhere in the containing artifact, such as a footnote index.
Though not commonly used in citation records, this could be used for referencing other articles in the abstract or explanatory notes.
Brief description of the related artifact
A brief description of the document or knowledge resource being referenced, suitable for display to a consumer.
A bibliographic citation for the related artifact. This text SHOULD be formatted according to an accepted citation format.
The artifact that is related to this Citation's cited artifact
The artifact that is related to this Citation Resource's cited artifact.
If multiple, used to represent alternative forms of the article that are not separate citations
Where, when and how the artifact was published. If multiple, used to represent alternative forms of the article that are not separate citations.
A common use is a journal article with a publication date and pagination for a print version and a different publication date for the online version of the same article.
The collection the cited article or artifact is published in
The collection the cited article or artifact is published in.
Kind of container (e.g. Periodical, database, or book)
Kind of container (e.g. Periodical, database, or book).
often coded with system http://terminology.hl7.org/CodeSystem/published-in-type, code D019991, and display Database
A formal identifier that is used to identify the database when it is represented in other formats, or referenced in a specification, model, design or an instance.
Name of the database or title of the book or journal.
ClinicalTrials.gov is a name of a database.
Name of or resource describing the publisher
Name of or resource describing the publisher.
Describes the form of the medium cited. Common codes are "Internet" or "Print". The CitedMedium value set has 6 codes. The codes internet, print, and offline-digital-storage are the common codes for a typical publication form, though internet and print are more common for study citations. Three additional codes (each appending one of the primary codes with "-without-issue" are used for situations when a study is published both within an issue (of a periodical release as commonly done for journals) AND is published separately from the issue (as commonly done with early online publication), to represent specific identification of the publication form not associated with the issue.
Volume number of journal or other collection in which the article is published
Volume number of journal or other collection in which the article is published.
Issue, part or supplement of journal or other collection in which the article is published
Issue, part or supplement of journal or other collection in which the article is published.
The date the article was added to the database, or the date the article was released
The date the article was added to the database, or the date the article was released.
The articleDate is the preferred element for expressing the publication date as structured data.
Text representation of the date on which the issue of the cited artifact was published
Text representation of the date on which the issue of the cited artifact was published.
The publicationDateText element is prefererntially used when a date is not represented in a form that can be handled as structured data in other elements.
Season in which the cited artifact was published
Season in which the cited artifact was published, e.g. Spring, Summer, Fall/Autumn, Winter.
The date the article was last revised or updated in the database
The date the article was last revised or updated in the database.
The lastRevisionDate is used for the cited article and not the date the Citation Resource is last revised.
Language(s) in which this form of the article is published
The language or languages in which this form of the article is published.
Entry number or identifier for inclusion in a database
Entry number or identifier for inclusion in a database.
Accession numbers may be used instead of or in addition to page numbers. Accession numbers are functionally identifiers when coupled with the identity of the database for which they are accession numbers. Accession numbers which are used for indexing citations in a dataset of citations should NOT be entered in Citation.citedArtifact.publicationForm.accessionNumber -- this use would be a type of Citation.identifier for the citation record itself.
Used for isolated representation of first page
Used for isolated representation of first page.
Used for isolated representation of last page
Used for isolated representation of last page.
Actual or approximate number of pages or screens. Distinct from reporting the page numbers.
Copyright notice for the full article or artifact
Copyright notice for the full article or artifact.
It is possible that different publication forms have different copyright notices.
Used for any URL for the article or artifact cited
Used for any URL for the article or artifact cited.
Code the reason for different URLs, e.g. abstract and full-text
A characterization of the object expected at the web location.
Categories that may be frequently used for study citations may include abstract, full-text, supplement, webpage, and doi-based.
Persistent URLs, like doi, are preferred.
Complex or externally created classification
Complex or externally created classification.
Examples relevant to study citations include MeSH Headings or Keywords that contain qualifier codings or sub-classifications, and include risk of bias assessments created by persons different from the creator of the citation record.
Extensions are always sliced by (at least) url
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Attribution of authors and other contributors
This element is used to list authors and other contributors, their contact information, specific contributions, and summary statements.
Need to support individualized and collective attribution of authorship and contributorship to people and groups.
Indication whether all authors are included in the entry content.
If list is incomplete, "et al" can be appended to Contributorship.summary.value for display purposes.
An individual entity named as a contributor
An individual entity named as a contributor, for example in the author list or contributor list.
Used to report contributorship in individualized ways.
The identity of the individual contributor
The identity of the individual contributor.
If naming a contributor without additional detail or further structured data, the display element within the Reference datatype may be used for a simple string without referencing another resource.
This element is used to support a data element used for citations that is not otherwise supported fully by FHIR HumanName datatype. In some citation summary styles (e.g. Medline), authors are presented with full spelling of their last name (family name) and initials for all forenames (first names, middle names, preceding names, given names). As the FHIR HumanName Datatype does not have a specific element for forename initials and this is common in citation usage, the element is added to contributorship.entry directly.
Organization affiliated with the contributor.
If naming an organization without additional detail or further structured data, the display element within the Reference datatype may be used for a simple string without referencing another resource.
The specific nature of an individual’s contribution with respect to the cited work.
The CreDiT taxonomy provides a way to encode contribution information. The purpose of CRediT is to provide transparency in contributions to scholarly published work, to enable improved systems of attribution, credit, and accountability.
The role of the contributor (e.g. author, editor, reviewer, funder)
The role of the contributor (e.g. author, editor, reviewer, funder).
Contributions with accounting for time or number
Contributions with accounting for time or number.
The time that the contribution was made.
Whether the contributor is the corresponding contributor for the role
Whether the contributor is the corresponding contributor for the role.
If there are multiple authors and one serves as the corresponding author, then that one would have correspondingContact = true.
Provides a numerical ranking to represent the degree of contributorship relative to other contributors, such as 1 for first author and 2 for second author.
Used to retain order of authorship as structured data
Used to record a display of the author/contributor list without separate data element for each list member
Used to record a display of the author/contributor list without separate data element for each list member.
Such as author list, contributorship statement, funding statement, acknowledgements statement, or conflicts of interest statement
Used most commonly to express an author list or a contributorship statement.
The format for the display string, such as author last name with first letter capitalized followed by forename initials.
Used to code the producer or rule for creating the display string
Used to code the producer or rule for creating the display string.
The display string for the author list, contributor list, or contributorship statement
The display string for the author list, contributor list, or contributorship statement.
Any additional information or content for the article or artifact
Any additional information or content for the article or artifact.