The seqic_*() functions require users to pass column names to each column related argument. This is more cumberson than, say, the trauma_performance() function or rmm() where users just have a few column-related arguments.
In the SEQIC functions, this causes users to have to do a lot of work to get the functions to run, especially for NEMSQA measures that are highly dimensional.
@samuelkordik had a great idea for the {nemsqar} package to make it possible to
- allow the function to find the columns based on standard NEMSIS naming conventions using regex under the hood
- allow users to still pass column names as an alternative
This could work for the {traumar}, maybe only for the seqic_*() functions given that other functions in the package do not require as many column arguments and this may not be as helpful. Instead of leaning on NEMSIS, we would lean on the NTDB data standard and use their naming conventions.
The
seqic_*()functions require users to pass column names to each column related argument. This is more cumberson than, say, thetrauma_performance()function orrmm()where users just have a few column-related arguments.In the SEQIC functions, this causes users to have to do a lot of work to get the functions to run, especially for NEMSQA measures that are highly dimensional.
@samuelkordik had a great idea for the {nemsqar} package to make it possible to
This could work for the {traumar}, maybe only for the
seqic_*()functions given that other functions in the package do not require as many column arguments and this may not be as helpful. Instead of leaning on NEMSIS, we would lean on the NTDB data standard and use their naming conventions.