Some time ago, CMS mandated collection of Ethnicity indicators. Specifically, upon registering a patient, we were required to ask if he/she was Hispanic/Latino. The acceptable responses were:
Y = Yes
N = No
D = Declined
U = Unavailable
We built a Customer Defined Query and attached the screen to the ADM Census tab for all patient types. The query was setup as a Demo Recall field to ensure the data would persist beyond the ADM File Maintenance Parameter.
Pulling data on ADM Report for time frame within ADM File Maintenance Parameters:
Detail DPM: ADM.PAT.main
xx.ethnicity
DAT=FREE
LEN=10
VAL=@cd.response[@urn,"MY.QUERY"]
Pulling data for time frame which exceeds ADM File Maintenance Parameters:
Say your ADM File Maintenance Parameters are only set to 90 days and you want to pull patients within a specific admission date range exceeding our parameters. Write the report using:
Detail: ABS.PAT.main
Index: ABS.PAT.adm.x
You have to look to the MRI.DRC DPM to pull the data. The following Footnote is a dummy fragment call that essentially opens a connection to your MRI database (of course, replace the “FAC” with your Facility code):
AL START %Z.rw.fragment(“”,”MRI.FAC”)
If you are familiar with reading Meditech’s Data Definitions, you’ll notice that the cd.response is stored in the following segment:
customer.defined.queries <—– segment
[medical.record, cd.query] <—– subscripts
Meditech teaches us that “subscripts” are keys to accessing data. Meditech’s website also teaches us that the link between ABS and MRI.DRC is:
ABS.PAT.mri.urn = MRI.DRC.medical.record
That means in an ABS report, you can use @mri.urn as the subscript to pull an MRI.DRC field. To finish up this example, create a custom field as follows:
xx.ethnicity
DAT=FREE
LEN=20
VAL=@MRI.DRC.cd.response[@mri.urn,"MY.QUERY"]
