Does the returned sc status contains the <INVALID OREF> error?

Add this line following the one I suggested:

if $$$ISERR(sc) $$$LOGERROR($system.Status.GetErrorText(sc)

Then check the event log after calling your component and post here what you find in the event log.

An integrity check also treats it as if it was a single file. This is only going to be more of an issue as the max size increses.

There is no other option for integrity check because in multi volume database a global can span across multiple volumes/files and a global structure must be fully scanned to check integrity.

If this is a concern, maybe splitting a global across multiple "small" (the concept of small may vary! 😁) database using subscript mapping can be an option.
Integrity check is performed at database/global level, not namespace/global level.

Evidently there is an issue where you reference MSH:9.2, without details of your rule definition is virtually impossible to guess where the problem is.

I'd suggest to check the returned %Status from the %FromFHIRJSON() method.

Instead of:

do ..FHIRAdapter.%FromFHIRJSON(pRequest.Payload.Read(),.pmReqFHIRobj,"HS.FHIR.Model.Resource.Bundle")

Use:

set sc=..FHIRAdapter.%FromFHIRJSON(pRequest.Payload.Read(),.pmReqFHIRobj,"HS.FHIR.Model.Resource.Bundle")

Then check the status.

There is also this recent announce from @Rob Tweed that mention support for legacy weblink applications:

mg_web for ObjectScript Developers
 

You may have the option of using Extended Global References and in particular Bracket Syntax with References to Databases.

In your code you need to change all your global references from:
^SYS("CommonConfig")
to
^[%dbConfig]SYS("CommonConfig")

Then, for normal situation where you want the %ALL mapping to apply, just use:
set %dbConfig=""
When you need to explicitly map it to a BARCONFIG database, then:
set %dbConfig="^^:ds:BARCONFIG"

This way you can switch from default %ALL mapping to "explicit reference" within your code.
In the example I used a % local variable (%dbConfig) to hold the "database name reference" because it has a global scope, you may use a different approach like a property in some of your classes, a macro with some reference (in a global?) or...whatever is appropriate for your environment.

Length 50

ClassMethod Count(i As %String) As %Integer
{
	f p=1:1:$l(i){i ")]}D>"[$e(i,p),$i(c)} q +$g(c)
}

Length: 77

ClassMethod Count(i As %String) As %Integer
{
	s i=$tr(i,":;8B=-^co~","") f p=1:1:$l(i){i ")]}D>"[$e(i,p),$i(c)} q +$g(c)
}

In addition, test case 1 & 5 & 9 have been modified/edited.

What does the file alert.log (in mgr dir as messages.log) contains?

irislib database is mounted as readonly database, so journal is disabled.

irislocaldata database contains items used internally by IRIS and journal is disabled by design.

This is standard/normal in any IRIS installation.

I doubt your issue is caused by these journal being disabled and I would not tamper default/standard journal configuration for system databases.

The class HS.FHIR.DTL.vR4.Model.Resource.Bundle is a registered object and cannot be used in a persistent class property.

A production/ensemble message, a request in your case, MUST be a %Persistent class.

BundleObject is a %DynamicObject and is not (does not extend) a %Presistent class.

In your messages.log do you see entries like:

[Generic.Event] VSS Writer: OnFreeze
......
......
[Generic.Event] VSS Writer: OnThaw

This is what is logged when a VSS snapshot is performed in windows.

In "well behaved Windows server" this two messages are less that a minute apart