Cached FHIR Profile not invalidated upon write

[rahul1]

Background

User Driven: https://discord.com/channels/905144809105260605/1194887284537954304

User has uploaded a custom profile as a StructureDefinition. However, when they upload a new version of the StructureDefintion is saved to the DB, the relevant Redis entry is not updated.

Repro

1. Upload test-profile.json
2. Upload test-encounter.json
3. Update the StructureDefinition resource created in step 1 with the following: test-profile-2.json (this removes a constraint on Encounter.identifier)
4. Upload test-encounter.json again

Expected Behavior

• Encounter fails validation on step 2
• Encounter passes validation on step 4

Actual Behavior

• Encounter fails validation both times

Relevant Code

medplum/packages/server/src/fhir/repo.ts

Lines 602 to 638 in f38c6b8

	private async loadProfile(url: string): Promise<StructureDefinition | undefined> {
	const redis = getRedis();
	const cacheKey = `Project/${this.context.project}/StructureDefinition/${url}`;
	// Try retrieving from cache
	const cachedProfile = await redis.get(cacheKey);
	if (cachedProfile) {
	return (JSON.parse(cachedProfile) as CacheEntry<StructureDefinition>).resource;
	}
	// Fall back to loading from the DB; descending version sort approximates version resolution for some cases
	const profile = await this.searchOne<StructureDefinition>({
	resourceType: 'StructureDefinition',
	filters: [
	{
	code: 'url',
	operator: Operator.EQUALS,
	value: url,
	},
	],
	sortRules: [
	{
	code: 'version',
	descending: true,
	},
	],
	});
	if (profile) {
	// Store loaded profile in cache
	await redis.set(
	cacheKey,
	JSON.stringify({ resource: profile, projectId: profile.meta?.project }),
	'EX',
	24 * 60 * 60 // 24 hours in seconds
	);
	}
	return profile;

[codyebberson]

Fixed in #3813