F

NameKindDescription
false_validattributeTrue if the value False is allowed.
FEEDER_AUDITclassThe FEEDER_AUDIT class defines the semantics of an audit trail which is constructed to
describe the origin of data that have been transformed into openEHR form and committed to the system.
FEEDER_AUDITartifact
feeder_auditrelationAudit trail from non-openEHR system of original commit of information
forming the content of this node, or from a conversion gateway which
has synthesised this node.
FEEDER_AUDIT_DETAILSclassAudit details for any system in a feeder system chain. Audit details here means
the general notion of who/where/when the information item to which the audit is
attached was created. None of the attributes is defined as mandatory, however, in
different scenarios, various combinations of attributes will usually be mandatory.
This can be controlled by specifying feeder audit details in legacy archetypes.
FEEDER_AUDIT_DETAILSartifact
feeder_system_auditrelationAny audit information for the information item from the feeder system,
if different from the originating system.
feeder_system_item_idsattributeIdentifiers used for the item in the feeder system, where the feeder system
is distinct from the originating system.
fillersrelation
FOLDERclassThe concept of a named folder.
FOLDERartifact
foldersrelationSub-folders of this FOLDER.
formalismattributename of the formalism, e.g. GLIF 1.0 , Proforma etc.
formattingattributeA format string of the form name:value; name:value... ,
e.g. "font-weight : bold; font-family : Arial; font-size : 12pt;".

Values taken from W3C CSS2 properties lists back-ground and font .
fractional_seconds_allowedattributeTrue if fractional seconds are allowed in the constrained Duration.
fragment_idoperationA part of, a fragment or a sub-function within an object.
Allows references to sub-parts of objects, such as a certain line and
character position in a text object. The syntax and semantics are
defined by the application responsible for the object.
functionattributeThe function of the Party in this participation (note that a given party
might participate in more than one way in a particular activity). This
attribute should be coded, but cannot be limited to the
HL7v3:ParticipationFunction vocabulary, since it is too limited and
hospital-oriented.