Where a Fact Is Stored¶
Some facts have more than one plausible home in FHIR: a resource has several dates, two elements can both hold a person, or one kind of record could be two resource types. A report, the EMR client and this guide have to read and write the same one, so each rule below names the element. The profile element named in each rule says the same thing in its own definition or comment, and the reportable fields in the Nexus Field CodeSystem read exactly these elements; Reportable Fields explains how. Where a field cannot reach the element yet, it is not reportable, and its concept says so; it never reads a nearby element instead.
Dates¶
- The date on a filed document is
DocumentReference.content.attachment.creation. When the document was filed to this chart isDocumentReference.date; when the documented service happened iscontext.period. A document is dated by the attachment's creation, falling back todateonly where the attachment carries none. - The date of a letter or a note is
Composition.event.period.start, set once when it is composed.Composition.datemoves on every amendment, andattester.timeis when it was signed. See the Composition profile. - When a specimen was collected is the lab report's
DiagnosticReport.effective[x], and each result Observation carries the same date on its owneffective[x]. No Specimen is written on its own. - The date of a billed service is on the Invoice line item, in the
nexus-invoice-service-dateextension.Invoice.dateis the billing date. - When a health card took effect and when it expires are the
period.startandperiod.endof the jurisdictional identifier on the Patient profile. - When an encounter happened is
Encounter.period.start, which is the date the encounter profile dates an encounter by.
People¶
- Who signed a note or letter is the
Composition.attesterwithmode = legal. A supervisor's sign-off and a co-signature are separate attesters, and a correction re-signs with a second legal attester. - Who made an observation is
Observation.performer. Who entered it, and who filed a received document to a chart, is anentereragent on a Provenance targeting the resource. A document'sauthenticatoris the sender's signer, never the clinic's user. A report cannot read who entered or filed a resource yet: the Provenance points at the resource, and a field reads only what the resource it reports reaches forward, so entered-by and filed-by are not reportable until the field grammar can follow a Provenance back. - A substitute decision-maker on a privacy directive is the directive's
Consent.performer, a RelatedPerson.Consent.provision.actoris whom the restriction is against.
Kinds of record¶
- A problem-list entry and a past medical history entry are both a Condition with category
problem-list-item, told apart byclinicalStatus: active, recurrence or relapse is on the live list; inactive, resolved or remission is history. A diagnosis made at an encounter or billed on a claim is categoryencounter-diagnosis. - A prevention is an Observation with its normal clinical category, marked by a coding under
the
nexus-emr-prevention-catalognaming system onObservation.code. - A letter written here is a Composition typed LOINC 51852-2; a note is a Composition typed
LOINC 34109-9. A note section is identified by
section.code, never by its title. - A normal range and a therapeutic range are both
Observation.referenceRange, told apart byreferenceRange.type:normalortherapeutic. A writer states the type rather than leaving a normal range untyped. A reader treats a range with no type as normal, as base FHIR defines it, so ranges written without one are still read as the normal range. - A drug's brand is the display of the prescription's DIN coding. The medication as the
prescriber wrote it is
medication[x].text. - A patient record with no
Patient.activeis in active use; base FHIR gives the element that meaning when missing, and the profile's comment repeats it for readers of converted records.
Not yet decided¶
- Whether a referral, a letter, a form or a scanned document is a request or a result. A referral is recorded as a ServiceRequest today, but one may also arrive or leave as a letter, a specialist's form or a scanned document, and which resource carries it in each case is not settled. Until it is, the referral fields read the ServiceRequest only, and no element records when a referral was sent.
- Where a received consult report is stored. One received electronically arrives as a DiagnosticReport; one received as a scan or fax as a DocumentReference. Which of the two the guide standardises on is decided with the question above; see Incoming reports.
- When a prescription was signed.
MedicationRequest.authoredOnis when it was written. Whether signing is recorded by stampingauthoredOnagain or as a Provenance on the prescription is not settled.