Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment vs http://hl7.org/fhir/us/odh/StructureDefinition/odh-PastOrPresentJob

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Observation
copyright	Used by permission of HL7 International, all rights reserved Creative Commons License	©2020+ HL7 International Public Health Work Group. Package hl7.fhir.us.odh#1.0.0 based on FHIR 4.0.1. Generated 2020-01-08. Links: Home | QA Report | Search | Version History external | CC0 external | Propose a change external	Values Differ
date	2022-04-20	2020-01-04	Values Differ
description	The US Core Observation Screening Assessment Profile meets the requirements of the US Core Data for Interoperability (USCDI) Assessments. To promote interoperability and adoption through common implementation, it sets the minimum expectations for the Observation Resource to record, search, and fetch observations representing the questions and responses to surveys and screening and assessment tools. For example, a social history status such as education or food insecurity or an assessment of the patient's cognitive, functional, or disability status. It can represent a single response, multiple responses, and multi-select "check all that apply" type questions. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource when using this profile. It provides the floor for standards development for specific use cases.	A Past or Present Occupation Observation is a clinical statement about the type of work done by a person in a job, as reported by that person. It includes a set of self-reported, related observations that remain associated with one-another to characterize the job and provide clinically-relevant information. It also can be used in a minor's record for the job(s) of people who share a home with the person (see optional related subject). A job is defined as a work situation, training position, or (potentially clinically-relevant) volunteer position held for a specified time period; for a given job, updates to Job Occupation, Past or Present Industry (Job Industry), Supervisory Level, or Employer would constitute a new job or volunteer position. A person can have more than one job at the same time and multiple jobs over time. Knowledge about a person's job(s) informs diagnosis and management of illness and injury; it also informs management of health in the work environment, regardless of whether a condition is work-related. While knowing about a person’s current job(s) is likely to be most important, some work-related health conditions can manifest after a long latency so a history of jobs can also provide valuable information. This set of related Job observations also can provide information for public health to locate infectious disease outbreaks and intervene to prevent further illness. Public health can also use these data to analyze work-related conditions such as silicosis, pesticide poisoning, and some types of cancer to identify Occupations, Industry sectors and Employers for whom interventions are needed to mitigate risk.	Values Differ
experimental
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreObservationScreeningAssessmentProfile	PastOrPresentJob	Values Differ
publisher	HL7 International - Cross-Group Projects	HL7 International Public Health Work Group	Values Differ
purpose
status	active
title	US Core Observation Screening Assessment Profile	Past Or Present Job	Values Differ
type	Observation
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment	http://hl7.org/fhir/us/odh/StructureDefinition/odh-PastOrPresentJob	Values Differ
version	6.0.0-ballot	1.3.0	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
Observation	C	0..*	Observation	Survey Observation us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present us-core-3: SHALL use UCUM for coded quantity units.	C	0..*	Observation	Past Or Present Job	Elements differ in short: 'Survey Observation' vs 'Past Or Present Job' Elements differ in definition: '\-' vs 'Related data elements for a current or previous job, as reported by the person, i.e., a work situation or position held for a specified time period. A person can have more than one job at the same time and multiple jobs over time, so the data related to each job must remain in the record in perpetuity. Each job should be recorded in a separate instance of PastOrPresentJob. A person’s job can be a social determinant of their health and information about a person’s job can support patient care, population health, and public health. In patient care, knowledge of a person’s past or present job(s) can impact recognition, diagnosis, management, and treatment of injuries and illnesses. These data also can be used for clinical decision support and to prompt discussion of preventive care measures. For example, a record of jobs that require prolonged time in the sun might prompt a health care provider to inquire if the person wears protective clothing or sunscreen while working. At a minimum, it is important to have a record of a person’s current job(s); i.e., the job(s) in which a person is engaged at the time that he or she presents to a health care provider, regardless of duration, and to retain that information over time. In the event a person recently stopped working (e.g. retired without another job, became unemployed or disabled and unable to work), the most recent job(s) is used instead of the current job(s).' Elements differ in comments: '\-' vs 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.'
id	Σ	0..1	id	Logical id of this artifact	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Extension Slice: Unordered, Open by value:url	Elements differ in short: 'Additional content defined by implementations' vs 'Extension' Elements differ in definition: '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 manageable, 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.' vs 'An Extension'
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	Business Identifier for observation	Σ	0..*	Identifier	Business Identifier for observation
basedOn	Σ	0..*	Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)	Fulfills plan, proposal or order	Σ	0..*	Reference(ServiceRequest)	The plan, proposal or order that is fulfilled in whole or in part by this observation	Elements differ in short: 'Fulfills plan, proposal or order' vs 'The plan, proposal or order that is fulfilled in whole or in part by this observation' Elements differ in definition: 'A plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed.' vs 'The plan, proposal or order that is fulfilled in whole or in part by this observation.' Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/CarePlan], CanonicalType[http://hl7.org/fhir/StructureDefinition/DeviceRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImmunizationRecommendation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/NutritionOrder], CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest]])
partOf	Σ	0..*	Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)	Part of referenced event	Σ	0..*	Reference(Procedure)	The larger procedure that this particular observation is a component or step	Elements differ in short: 'Part of referenced event' vs 'The larger procedure that this particular observation is a component or step' Elements differ in definition: 'A larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure.' vs 'The larger procedure that this particular observation is a component or step.' Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationAdministration], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationDispense], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationStatement], CanonicalType[http://hl7.org/fhir/StructureDefinition/Procedure], CanonicalType[http://hl7.org/fhir/StructureDefinition/Immunization], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Procedure]])
status	?!SΣ	1..1	code	registered | preliminary | final | amended + Binding: ?? (required): Codes providing the status of an observation.	?!Σ	1..1	code	registered | preliminary | final | amended + Binding: ?? (required): Codes providing the status of an observation.	Elements differ in definition for mustSupport: 'true' vs 'false'
Slices for category	S	1..*	CodeableConcept	Classification of type of observation Slice: Unordered, Open by pattern:$this Binding: ?? (preferred): Codes for high level observation categories.		0..1	CodeableConcept	Classification of type of observation Binding: ?? (preferred): Codes for high level observation categories.	Elements differ in definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '1' vs '0' Element maximum cardinalities differ: '2147483647' vs '1'
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system	Σ	1..*	Coding	Code defined by a terminology system Slice: Unordered, Open by value:code	Element minimum cardinalities differ: '0' vs '1'
text	Σ	0..1	string	Plain text representation of the concept	Σ	0..1	string	Plain text representation of the concept
code	SΣ	1..1	CodeableConcept	Type of observation (code / type) Binding: ?? (preferred)	Σ	1..1	CodeableConcept	Type of observation (code / type) Binding: ?? (example): Codes identifying names of simple observations.	Elements differ in definition for mustSupport: 'true' vs 'false' Example/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningAssessmentProfile
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system	Σ	1..*	Coding	Code defined by a terminology system Slice: Unordered, Open by value:code	Element minimum cardinalities differ: '0' vs '1'
text	Σ	0..1	string	Plain text representation of the concept	Σ	0..1	string	Plain text representation of the concept
subject	SΣ	1..1	Reference(US Core Patient Profile)	Who and/or what the observation is about	Σ	1..1	Reference(US Core Patient Profile)	The subject of an observation	Elements differ in short: 'Who and/or what the observation is about' vs 'The subject of an observation' Elements differ in definition: 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.' vs 'The subject of an observation.' Elements differ in definition for mustSupport: 'true' vs 'false'
focus	ΣTU	0..*	Reference(Resource)	What the observation is about, when it is not about the subject of record	Σ	0..*	Reference(RelatedPerson)	What the observation is about, when it is not about the subject of record	Elements differ in comments: 'Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., "Blood Glucose") and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode].' vs 'This is used only when conveying job information of person(s) who share a home with a patient who is a child. It represents the relationship of the person holding this Job Occupation to the patient.'
encounter	Σ	0..1	Reference(Encounter)	Healthcare event during which this observation is made	Σ	0..1	Reference(Encounter)	Healthcare event during which this observation is made
effective[x]	SΣC	0..1	dateTime S, Period, Timing, instant	Clinically relevant time/time-period for observation us-core-1: Datetime must be at least to day.	Σ	1..1	Period	Clinically relevant time/time-period for observation Slice: Unordered, Closed by type:$this	Elements differ in definition: 'The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time".' vs 'The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.' Elements differ in comments: 'At least a date should be present unless this observation is a historical report.' vs 'At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the [Timing] datatype which allow the measurement to be tied to regular life events.' Elements differ in definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '0' vs '1'
issued	Σ	0..1	instant	Date/Time this version was made available	Σ	0..1	instant	Date/Time this version was made available
performer	SΣ	0..*	Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core CareTeam Profile | US Core RelatedPerson Profile)	Who is responsible for the observation	Σ	0..*	Reference(Practitioner | Organization | US Core Patient Profile | RelatedPerson)	Who is responsible for the observation	Elements differ in definition for mustSupport: 'true' vs 'false'
value[x]	SΣC	0..1	Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	Actual result	ΣC	0..1	Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	Actual result Slice: Unordered, Open by type:$this	Elements differ in comments: 'An observation may have a value if it represents an individual survey, screening, or assessment question and answer pair. An observation should not have a value if it represents a multi-question or multi-select “check all that apply” responses. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value.' vs 'An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section] below.' Elements differ in definition for mustSupport: 'true' vs 'false'
dataAbsentReason	SC	0..1	CodeableConcept	Why the result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.	C	0..1	CodeableConcept	The reason that there is no value available for the Occupation. Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.	Elements differ in short: 'Why the result is missing' vs 'The reason that there is no value available for the Occupation.' Elements differ in definition: 'Provides a reason why the expected value in the element Observation.value[x] is missing.' vs 'The reason that there is no value available for the Occupation.' Elements differ in comments: '"Null" or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For a given LOINC question, if the LOINC answer list includes concepts such as 'unknown' or 'not available', they should be used for Observation.value. Where these concepts are not part of the value set for Observation.value, the Observation.dataAbsentReason can be used if necessary and appropriate.' vs 'Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "specimen unsatisfactory". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.' Elements differ in definition for mustSupport: 'true' vs 'false'
interpretation		0..*	CodeableConcept	High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations.		0..0			Element maximum cardinalities differ: '2147483647' vs '0'
note		0..*	Annotation	Comments about the observation		0..*	Annotation	Comments about the observation
bodySite		0..1	CodeableConcept	Observed body part Binding: ?? (example): Codes describing anatomical locations. May include laterality.		0..0			Element maximum cardinalities differ: '1' vs '0'
method		0..1	CodeableConcept	How it was done Binding: ?? (example): Methods for simple observations.		0..0			Element maximum cardinalities differ: '1' vs '0'
specimen		0..1	Reference(Specimen)	Specimen used for this observation		0..0			Element maximum cardinalities differ: '1' vs '0'
device		0..1	Reference(Device | DeviceMetric)	(Measurement) Device		0..0			Element maximum cardinalities differ: '1' vs '0'
referenceRange	C	0..*	BackboneElement	Provides guide for interpretation	C	0..0			Element maximum cardinalities differ: '2147483647' vs '0'
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
low	C	0..1	??	Low Range, if relevant	C	0..1	??	Low Range, if relevant
high	C	0..1	??	High Range, if relevant	C	0..1	??	High Range, if relevant
type		0..1	CodeableConcept	Reference range qualifier Binding: ?? (preferred): Code for the meaning of a reference range.		0..1	CodeableConcept	Reference range qualifier Binding: ?? (extensible): Code for the meaning of a reference range.
appliesTo		0..*	CodeableConcept	Reference range population Binding: ?? (example): Codes identifying the population the reference range applies to.		0..*	CodeableConcept	Reference range population Binding: ?? (extensible): Codes identifying the population the reference range applies to.
age		0..1	Range	Applicable age range, if relevant		0..1	Range	Applicable age range, if relevant
text		0..1	string	Text based reference range in an observation		0..1	string	Text based reference range in an observation
hasMember	SΣ	0..*	Reference(US Core Observation Screening Assessment Profile S | QuestionnaireResponse | MolecularSequence)	Reference to panel or multi-select responses	Σ	0..0			Elements differ in short: 'Reference to panel or multi-select responses' vs 'Related resource that belongs to the Observation group' Elements differ in definition: 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys, screenings, and assessments and multi-select questions.' vs 'This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.' Elements differ in comments: 'This grouping element is used to represent surveys, screenings, and assessments that group several questions together or individual questions with “check all that apply” responses. For example in the simplest case a flat multi-question survey where the "panel" observation is the survey instrument itself and instead of an `Observation.value` the `hasMember` element references other Observation that represent the individual questions answer pairs. When there is a heirarchical grouping of questions, the observation "panels" can be nested. Because surveys, screenings, and assessments can be arbitrarily complex structurally, not all structures can be represented using this Observation grouping pattern.' vs 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes] below. Note that a system may calculate results from [QuestionnaireResponse] into a final score and represent the score as an Observation.' Elements differ in definition for mustSupport: 'true' vs 'false' Element maximum cardinalities differ: '2147483647' vs '0'
derivedFrom	SΣ	0..*	Reference(US Core Observation Screening Assessment Profile S | QuestionnaireResponse | US Core DocumentReference Profile | ImagingStudy | Media | MolecularSequence)	Related Observation(s) or other resource the observation is made from	Σ	0..*	Reference(DocumentReference | Media | QuestionnaireResponse | Observation)	Related measurements the observation is made from	Elements differ in short: 'Related Observation(s) or other resource the observation is made from' vs 'Related measurements the observation is made from' Elements differ in definition: 'Observations or or other resource such as a QuestionnaireResponse from which this observation value is derived.' vs 'The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.' Elements differ in definition for mustSupport: 'true' vs 'false' Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation]])
component	Σ	0..*	BackboneElement	Component results	Σ	0..*	BackboneElement	Component results Slice: Unordered, Open by value:code.coding.code
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
code	Σ	1..1	CodeableConcept	Type of component observation (code / type) Binding: ?? (example): Codes identifying names of simple observations.	Σ	1..1	CodeableConcept	Type of component observation (code / type) Binding: ?? (example): Codes identifying names of simple observations.
value[x]	Σ	0..1	Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	Actual component result	Σ	0..1	Quantity, CodeableConcept, string, Range, Ratio, SampledData, time, dateTime, Period	Actual component result	Elements differ in comments: 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section] below.' vs 'If there is no coded value available for the Industry, the narrative description SHALL be expressed using originalText. The CDC_Census system has been used by public health programs to classify industry and occupation when only a text description has been collected. The PHIN VADS Hot Topics for ODH includes crosswalk tables from Industry_NAICS_Detail_(ODH) values to Industry_CDC_Census_2010 values.'
dataAbsentReason	C	0..1	CodeableConcept	Why the component result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.	C	0..1	CodeableConcept	Why the component result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.
interpretation		0..*	CodeableConcept	High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations.		0..*	CodeableConcept	High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations.
referenceRange		0..*	See referenceRange (Observation)	Provides guide for interpretation of component result		0..0			Element maximum cardinalities differ: '2147483647' vs '0'
Documentation for this format