Open reeager opened 3 months ago
We are creating the logical Ids for the following resources in the pattern described below:
We will be generating the above ids without spaces
, tildes
and perionds
.
But the bundleId
& observationIds
tend to be more than 64 characters.
@reeager @raphaelvp @ratheesh-kr @shah
@reeager periods can be used- update made.
For Consent: mrn, assigning auth, Organization (custodian).
The following are the generic id-primitive
and dateTime-primitive
rules that FHIR follows.
id-primitive
id
primitive in FHIR must adhere to specific constraints to ensure uniqueness and consistency:
^[A-Za-z0-9\-\.]{1,64}$
dateTime-primitive
dateTime
primitive in FHIR follows a pattern derived from ISO 8601. It can represent:
YYYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm]
YYYY-MM-DD
YYYY-MM
YYYY
@reeager @shah @raphaelvp
@reeager ,
~
as the concatenation string for each ID. visit_number
to be used for creating the IDs in Encounter
and Observation
? RECORDED_TIME
inside the screening CSV. So should we use that as the period:start
/message_date
? Rejection
for an incorrect format of the RECORDED_TIME
we may not have control over the format which will be then used in the ID generation process.@shah @raphaelvp @ratheesh-kr
@alan-francis
@reeager,
Please provide clarifications for the following:
visit_number
, if it needs to derived, specify the logic and source data to derive from.RECORDED_TIME
is incorrectly formatted, it will fail for other fields also.@reeager : So we can use the ENCOUNTER_ID
from the SCREENING
csv for visit_number
. Also as this ENCOUNTER_ID
is not a mandatory one and we are generating this if not available from FACILITY_ID
and PAT_MRN_ID
, we can do the same for visit_number
as well.
@shah @raphaelvp @ratheesh-kr
Please fix logical ids to continue to be unique but must remove the following:
This is to ensure the IDs are meeting R4.