1.8.0

What's Changed

• feat: add read_multiline_json_with_details by @mikix in #23

Full Changelog: v1.7.0...v1.8.0

1.7.0

What's Changed

• schema: expand Period schemas, if either of the fields are present by @mikix in #21

Full Changelog: v1.6.0...v1.7.0

1.6.0

What's Changed

• json: add recursive=False arguments to ndjson reader/lister by @mikix in #20

Full Changelog: v1.5.1...v1.6.0

1.5.1

What's Changed

• fix: provide status code in http error messages by @mikix in #18

Full Changelog: v1.5.0...v1.5.1

1.5.0

What's Changed

• feat: add FhirClient, a simple FHIR server client with retries by @mikix in #16

Full Changelog: v1.4.0...v1.5.0

1.4.0

What's Changed

• feat(json): add transparent support for .gz files by @mikix in #15

Full Changelog: v1.3.1...v1.4.0

1.3.1

This release prevents pyarrow_schema_from_rows from loading the rows argument into memory all at once. Now it will simply iterate over the rows, allowing larger-than-memory batches of rows.

1.3.0

This release adds support for extensions on primitive types. I.e. it adds support for "sunder" fields like _status (sibling of status).

See http://hl7.org/fhir/R4/json.html#primitive for more details.

Example:

{
  "birthDate": "1970-03-30",
  "_birthDate": {
    "id": "314159",
    "extension": [{
       "url": "http://example.org/fhir/StructureDefinition/text",
       "valueString": "Easter 1970"
    }]
  }
}

These fields will be in the resulting schema if they are present in the input rows, else they will be left off.

1.2.1

This release just prepares for an upcoming fhirclient release which tweaks how date & time handling works. No functional changes.

1.2.0

This release adds three new methods for reading NDJSON:

• list_multiline_json_in_dir: scans for files & their resource types
• read_multiline_json: returns line by line results from a file
• read_multiline_json_from_dir: returns line by line results from a folder

Headline features:

• Lets you filter by FHIR resource type (by actually inspecting the contents of a file, rather than playing guessing games with filenames)
  • But these functions are not restricted to FHIR-based JSON, you can read arbitrary multi-line JSON too
• Transparently handles I/O and decode errors by logging a warning and continuing - these are designed for bulk processing
• You can read from remote filesystem locations using the optional fsspec support
• Supports both NDJSON and JSON Lines formats