Open Nelly-Barret opened 1 week ago
For now, I build resource identifiers like this:
{ identifier: { value: 'ExaminationRecord/155' }, resourceType: 'ExaminationRecord', .... }
I am thinking on shifting to:
{ identifier: { value: 155 }, resourceType: 'ExaminationRecord', .... }
I first need to check whether FHIR can handle int identifiers or not. In any case, this might be better to have just the int identifier because:
ExaminationRecord/X
However, building this Resource/Id identifier when we need it might be costly in the end. To be seen
For now, I build resource identifiers like this:
I am thinking on shifting to:
I first need to check whether FHIR can handle int identifiers or not. In any case, this might be better to have just the int identifier because:
ExaminationRecord/X
which we have to split)However, building this Resource/Id identifier when we need it might be costly in the end. To be seen