@ovok/core 0.2.56 → 0.2.58

package/dist/client/observation/services/ecg.js

@@ -33,10 +33,14 @@ class EcgService extends base_observation_service_1.BaseObservationService {
         const heartRate = castedMeasurement.heartRate;
         const diagramPoints = castedMeasurement.diagramPoints;
         if (diagramPoints === null || diagramPoints === void 0 ? void 0 : diagramPoints.length) {
+            const duration = castedMeasurement.duration;
+            const period = typeof duration === "number" && Number.isFinite(duration) && duration > 0
+                ? (duration * 1000) / diagramPoints.length
+                : 1;
             values.push({
                 valueSampledData: {
                     origin: { value: 0, unit: "mV" },
-                    period: 1,
+                    period,
                     dimensions: 1,
                     data: diagramPoints.join(" "),
                 },
@@ -76,7 +80,12 @@ class EcgService extends base_observation_service_1.BaseObservationService {
                             ],
                         },
                         id: "measurement-duration",
-                        valueInteger: castedMeasurement.duration,
+                        valueQuantity: {
+                            value: castedMeasurement.duration,
+                            unit: "s",
+                            code: "s",
+                            system: "http://unitsofmeasure.org",
+                        },
                     },
                 ],
             },

package/dist/conformance/capability-requirements.d.ts

@@ -0,0 +1,31 @@
+import { CapabilityStatement } from "@medplum/fhirtypes";
+/**
+ * What a server must support for `@ovok/core` to work.
+ *
+ * `kind: requirements` rather than `capability`, and the distinction is the
+ * whole point. A `capability` statement would describe what this SDK CAN
+ * issue — and since `OvokClient extends MedplumClient` with no narrowing, the
+ * honest answer to that is "every interaction Medplum has", which tells a
+ * consumer nothing. `requirements` inverts it: here is the surface this
+ * library itself depends on, so pointing it at a server becomes a checkable
+ * proposition rather than a hope.
+ *
+ * Scope is therefore the SDK's OWN methods. Generic CRUD reached through the
+ * inherited Medplum client is the consuming application's business: that
+ * application knows which resources it touches, and this library does not
+ * require them.
+ *
+ * `implementation` is absent deliberately — FHIR forbids it for any kind but
+ * `instance`, and a client library has no endpoint to describe anyway. It
+ * cannot serve this at `/metadata`; it is published as a static artifact and
+ * exported so a consumer can compare it against a server's own statement.
+ *
+ * NOT DESCRIBED HERE, because a CapabilityStatement structurally cannot:
+ * seven of the SDK's ten HTTP call sites are ordinary REST, not FHIR —
+ * `POST /ai/session`, `POST /ai/fhir/search`, `POST /bots?identifier=`, and
+ * the auth surface (register, change-password, reset-password, Apple and
+ * Google sign-in, account deletion). Those are OpenAPI's job and are
+ * documented there. A conformance resource pretending to carry them would be
+ * readable by no FHIR client and no OpenAPI tool.
+ */
+export declare const OVOK_CORE_REQUIREMENTS: CapabilityStatement;

package/dist/conformance/capability-requirements.js

@@ -0,0 +1,99 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.OVOK_CORE_REQUIREMENTS = void 0;
+/**
+ * What a server must support for `@ovok/core` to work.
+ *
+ * `kind: requirements` rather than `capability`, and the distinction is the
+ * whole point. A `capability` statement would describe what this SDK CAN
+ * issue — and since `OvokClient extends MedplumClient` with no narrowing, the
+ * honest answer to that is "every interaction Medplum has", which tells a
+ * consumer nothing. `requirements` inverts it: here is the surface this
+ * library itself depends on, so pointing it at a server becomes a checkable
+ * proposition rather than a hope.
+ *
+ * Scope is therefore the SDK's OWN methods. Generic CRUD reached through the
+ * inherited Medplum client is the consuming application's business: that
+ * application knows which resources it touches, and this library does not
+ * require them.
+ *
+ * `implementation` is absent deliberately — FHIR forbids it for any kind but
+ * `instance`, and a client library has no endpoint to describe anyway. It
+ * cannot serve this at `/metadata`; it is published as a static artifact and
+ * exported so a consumer can compare it against a server's own statement.
+ *
+ * NOT DESCRIBED HERE, because a CapabilityStatement structurally cannot:
+ * seven of the SDK's ten HTTP call sites are ordinary REST, not FHIR —
+ * `POST /ai/session`, `POST /ai/fhir/search`, `POST /bots?identifier=`, and
+ * the auth surface (register, change-password, reset-password, Apple and
+ * Google sign-in, account deletion). Those are OpenAPI's job and are
+ * documented there. A conformance resource pretending to carry them would be
+ * readable by no FHIR client and no OpenAPI tool.
+ */
+exports.OVOK_CORE_REQUIREMENTS = {
+    resourceType: "CapabilityStatement",
+    id: "ovok-core-requirements",
+    url: "https://fhir.ovok.com/fhir/CapabilityStatement/ovok-core-requirements",
+    name: "OvokCoreClientRequirements",
+    title: "@ovok/core — server requirements",
+    status: "active",
+    /*
+     * The date this STATEMENT was last revised, which FHIR requires and which
+     * is not "now" — a statement that restamped itself on every read would
+     * report change where there is none. Bump it with `software.version` when
+     * the declared surface actually moves.
+     */
+    date: "2026-09-19",
+    kind: "requirements",
+    description: "The FHIR surface a server must provide for the @ovok/core client library's own methods to function.",
+    software: {
+        name: "@ovok/core",
+        version: "0.2.57",
+    },
+    fhirVersion: "4.0.1",
+    format: ["json"],
+    rest: [
+        {
+            mode: "client",
+            documentation: "Issued by the SDK's own methods. Interactions a consuming application makes through the inherited Medplum client are not this library's requirement.",
+            interaction: [
+                {
+                    code: "transaction",
+                    /*
+                     * `createQuestionnaireResponseWithObservations` posts a
+                     * `Bundle type=transaction` carrying the QuestionnaireResponse and
+                     * its Observations together. Atomicity is why it is a transaction
+                     * and not a batch: a response saved without its observations is a
+                     * record that reads as complete and is not.
+                     */
+                    documentation: "createQuestionnaireResponseWithObservations submits one transaction Bundle so the response and its observations land together or not at all.",
+                },
+            ],
+            resource: [
+                {
+                    type: "Observation",
+                    interaction: [{ code: "create" }],
+                    operation: [
+                        {
+                            name: "lastn",
+                            /*
+                             * Ovok's own canonical, not HL7's. The server operation
+                             * diverges on every parameter — `patient` as a string rather
+                             * than `subject` as a Reference, `max` as a string rather than
+                             * an integer, one comma-separated `code` rather than a
+                             * repeating one, and no category grouping at all.
+                             */
+                            definition: "https://fhir.ovok.com/fhir/OperationDefinition/observation-lastn",
+                            documentation: "getLatestObservationsByCodes reads the most recent Observations per code for one patient.",
+                        },
+                    ],
+                },
+                {
+                    type: "QuestionnaireResponse",
+                    interaction: [{ code: "create" }],
+                    documentation: "Created as an entry of the transaction Bundle above, never on its own by this library.",
+                },
+            ],
+        },
+    ],
+};

package/dist/index.d.ts

@@ -926,3 +926,4 @@ export { OvokClient } from "./client/ovok-client";
 export * from "./hooks";
 export * from "./utils";
 export * from "./client/observation/services";
+export * from "./conformance/capability-requirements";

package/dist/index.js

@@ -47,3 +47,4 @@ Object.defineProperty(exports, "OvokClient", { enumerable: true, get: function (
 __exportStar(require("./hooks"), exports);
 __exportStar(require("./utils"), exports);
 __exportStar(require("./client/observation/services"), exports);
+__exportStar(require("./conformance/capability-requirements"), exports);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ovok/core",
-  "version": "0.2.56",
+  "version": "0.2.58",
   "private": false,
   "main": "dist/index.js",
   "types": "dist/index.d.ts",